[[["易于理解","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-03。"],[[["This page details AlloyDB for PostgreSQL's database flags, which are used to enable and manage the service's unique features."],["Flags marked for instance restarts will cause AlloyDB to restart the instance whenever they are changed, and these changes will persist until modified again."],["`alloydb.enable_pgaudit` controls the `pgaudit` extension's availability and requires an instance restart after being set to `on`, enabling detailed audit logging, but has compatibility warnings with `logging_collector`."],["`alloydb.log_throttling_window` manages duplicate log message recording within a specified timeframe, with a value greater than 0 preventing immediate duplicate logs, while 0 logs all duplicates."],["`alloydb.promote_cancel_to_terminate` allows for the conversion of query cancellation requests into forced termination requests, preventing stuck backends and log replay issues when set to true."]]],[]]