[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC):2025-04-11。"],[[["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."]]],[]]