[[["わかりやすい","easyToUnderstand","thumb-up"],["問題の解決に役立った","solvedMyProblem","thumb-up"],["その他","otherUp","thumb-up"]],[["わかりにくい","hardToUnderstand","thumb-down"],["情報またはサンプルコードが不正確","incorrectInformationOrSampleCode","thumb-down"],["必要な情報 / サンプルがない","missingTheInformationSamplesINeed","thumb-down"],["翻訳に関する問題","translationIssue","thumb-down"],["その他","otherDown","thumb-down"]],["最終更新日 2025-04-09 UTC。"],[[["Datastream utilizes the PostgreSQL WAL transaction log, stored in WAL files, to capture changes made to the database tables."],["Setting the `max_slot_wal_keep_size` parameter is recommended to prevent the WAL file from consuming excessive storage, especially during long-running transactions, though it is not supported by certain databases like Cloud SQL and AlloyDB."],["The `statement_timeout` parameter can be configured to mitigate latency from prolonged transactions, serving as an alternative control for databases not supporting `max_slot_wal_keep_size`."],["If you need more than 10 streams, you must adjust the `max_replication_slots` and `max_wal_senders` parameters based on the number of streams or replication slots you are using in your database."],["Setting `wal_sender_timeout` to `0` or a value of 10 minutes or greater is advised for better performance."]]],[]]