[[["わかりやすい","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-11 UTC。"],[[["This page details specific database flags used by AlloyDB for PostgreSQL to manage its unique features, with a comprehensive list available at the provided link."],["Certain flags, marked with \"Instance restarts,\" require an instance reboot when they are set, removed, or modified, and their values persist until further changes."],["The `alloydb.enable_pgaudit` flag controls the availability of the `pgaudit` extension, requiring both the flag to be turned `on` and an instance restart to utilize the `CREATE EXTENSION` command, noting specific compatibility warnings with the `logging_collector` in AlloyDB Omni."],["The `alloydb.log_throttling_window` flag prevents duplicate log messages from being recorded within a specified time frame, defined by the integer value, with `0` recording all duplicates."],["Setting `alloydb.promote_cancel_to_terminate` to `true` converts cancellation requests into forced termination requests, helping to avoid stuck backends."]]],[]]