[[["易于理解","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-09。"],[[["This page details the database flags specific to AlloyDB for PostgreSQL, which are used to manage unique service features, and a list of all database flags can be found in the Supported database flags page."],["The `alloydb.enable_pgaudit` flag controls the availability of the `pgaudit` extension, requires instance restarts when modified, and should be set in coordination with the PostgreSQL `logging_collector` parameter to avoid audit log loss."],["The `alloydb.log_throttling_window` flag, which does not require instance restarts, determines whether duplicate log messages are recorded within a specified time window."],["The `alloydb.promote_cancel_to_terminate` flag, when set to `true`, transforms query cancellation requests into forced backend termination requests to prevent issues like stuck backends, and does not require an instance restart."],["The `alloydb.pg_shadow_select_role` flag, which does not require an instance restart, defines the name of the PostgreSQL role that is granted permission to query the `pg_shadow` view."]]],[]]
