[[["容易理解","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-08-17 (世界標準時間)。"],[[["\u003cp\u003eThis page provides a comprehensive list of database flags supported by AlloyDB Omni, which are used for various operations such as adjusting parameters and tuning instances.\u003c/p\u003e\n"],["\u003cp\u003eEach flag in the table has a default value, which AlloyDB Omni sets in a new instance unless a different value is specified during creation.\u003c/p\u003e\n"],["\u003cp\u003eThe "Restart required" column indicates whether AlloyDB Omni needs to be restarted after a flag is set, removed, or modified.\u003c/p\u003e\n"],["\u003cp\u003eThe "Replica restrictions" column identifies flags that need to be set on replica instances before being set on the primary, and ensures the replica value is equal to or greater than the primary's.\u003c/p\u003e\n"],["\u003cp\u003eClicking on a flag's name provides detailed information on its specific usage.\u003c/p\u003e\n"]]],[],null,["# Supported database flags\n\nSelect a documentation version: Current (16.8.0)keyboard_arrow_down\n\n- [Current (16.8.0)](/alloydb/omni/current/docs/reference/database-flags)\n- [16.8.0](/alloydb/omni/16.8.0/docs/reference/database-flags)\n- [16.3.0](/alloydb/omni/16.3.0/docs/reference/database-flags)\n- [15.12.0](/alloydb/omni/15.12.0/docs/reference/database-flags)\n- [15.7.1](/alloydb/omni/15.7.1/docs/reference/database-flags)\n- [15.7.0](/alloydb/omni/15.7.0/docs/reference/database-flags)\n\n\u003cbr /\u003e\n\nAlloyDB Omni supports all database flags provided by standard [PostgreSQL](https://www.postgresql.org/docs/16/index.html) versions. This page lists the database flags that AlloyDB Omni provides in addition to the standard database flags.\n\n\u003cbr /\u003e\n\nYou use database flags for many operations, including adjusting PostgreSQL\nparameters, adjusting options, and configuring and tuning instances.\n\nFor more information about setting database flags in\nAlloyDB Omni, see [Configure AlloyDB Omni database flags](/alloydb/omni/current/docs/configure-database-flags).\n\nAlloyDB Omni flags\n------------------\n\nThe table's other columns contain additional information\nabout each AlloyDB Omni flag:pG_\n\n- Click a flag name to see its usage instructions.\n\n- The **Default value** column displays the value that\n AlloyDB Omni sets for this flag in a new instance, unless you specify a different value when creating the instance.\n\n **Standard default** indicates that the flag has a default value that's not\n set by AlloyDB Omni. To learn more, click the flag's name.\n- In the **Restart required** column, **Yes** indicates that\n you need to restart AlloyDB Omni when you set, remove, or\n modify the flag on the instance. The flag's value persists for the\n instance until you modify it again.\n\n- In the **Replica restrictions** column, **Yes** indicates the following\n restrictions on how you can use the flag:\n\n - Before setting this flag on your cluster's primary instance, set\n the flag on each of your cluster's replica instances.\n\n - If the primary instance has this flag set, then the value of this\n flag on any replica instance must be equal to or greater\n than the primary instance's value for this flag.\n\n \u003cbr /\u003e\n\n[A](#postgres-a) \\| [C](#postgres-c) \\| [D](#postgres-d) \\| [E](#postgres-e) \\| [F](#postgres-f) \\| [G](#postgres-g) \\| [H](#postgres-h) \\| [I](#postgres-i) \\| [J](#postgres-j) \\| [L](#postgres-l) \\| [M](#postgres-m) \\| [O](#postgres-o) \\| [P](#postgres-p) \\| [R](#postgres-r) \\| [S](#postgres-s) \\| [T](#postgres-t) \\| [V](#postgres-v) \\| [W](#postgres-w)\n\nStandard PostgreSQL flags that need restart\n-------------------------------------------\n\nThe following standard PostgreSQL flags require a restart of AlloyDB Omni when you set, remove, or modify the flag on the instance. The flag's value persists for the instance until you modify it again.\n\n- [autovacuum_freeze_max_age](https://www.postgresql.org/docs/16/runtime-config-autovacuum.html#GUC-AUTOVACUUM-FREEZE-MAX-AGE)\n- [autovacuum_max_workers](https://www.postgresql.org/docs/16/runtime-config-autovacuum.html#GUC-AUTOVACUUM-MAX-WORKERS)\n- [autovacuum_multixact_freeze_max_age](https://www.postgresql.org/docs/16/runtime-config-autovacuum.html#GUC-AUTOVACUUM-MULTIXACT-FREEZE-MAX-AGE)\n- [cron.database_name](https://github.com/citusdata/pg_cron#what-is-pg_cron)\n- [cron.log_run](https://github.com/citusdata/pg_cron/blob/main/src/pg_cron.c)\n- [cron.log_statement](https://github.com/citusdata/pg_cron/blob/main/src/pg_cron.c)\n- [cron.max_running_jobs](https://github.com/citusdata/pg_cron/blob/main/src/pg_cron.c)\n- [max_connections](https://www.postgresql.org/docs/16/runtime-config-connection.html#GUC-MAX-CONNECTIONS)\n- [max_locks_per_transaction](https://www.postgresql.org/docs/16/runtime-config-locks.html#GUC-MAX-LOCKS-PER-TRANSACTION)\n- [max_logical_replication_workers](https://www.postgresql.org/docs/16/runtime-config-replication.html#GUC-MAX-LOGICAL-REPLICATION-WORKERS)\n- [max_pred_locks_per_page](https://www.postgresql.org/docs/16/runtime-config-locks.html#GUC-MAX-PRED-LOCKS-PER-PAGE)\n- [max_pred_locks_per_relation](https://www.postgresql.org/docs/16/runtime-config-locks.html#GUC-MAX-PRED-LOCKS-PER-RELATION)\n- [max_pred_locks_per_transaction](https://www.postgresql.org/docs/16/runtime-config-locks.html#GUC-MAX-PRED-LOCKS-PER-TRANSACTION)\n- [max_prepared_transactions](https://www.postgresql.org/docs/16/runtime-config-resource.html#GUC-MAX-PREPARED-TRANSACTIONS)\n- [max_replication_slots](https://www.postgresql.org/docs/16/runtime-config-replication.html#GUC-MAX-REPLICATION-SLOTS)\n- [max_wal_senders](https://www.postgresql.org/docs/16/runtime-config-replication.html#GUC-MAX-WAL-SENDERS)\n- [max_worker_processes](https://www.postgresql.org/docs/16/runtime-config-resource.html#GUC-MAX-WORKER-PROCESSES)\n- [old_snapshot_threshold](https://www.postgresql.org/docs/16/runtime-config-resource.html#GUC-OLD-SNAPSHOT-THRESHOLD)\n- [pg_stat_statements.max](https://www.postgresql.org/docs/16/pgstatstatements.html#id-1.11.7.38.8)\n- [pglogical.batch_inserts](https://github.com/2ndQuadrant/pglogical#configuration-options)\n- [pglogical.synchronous_commit](https://github.com/2ndQuadrant/pglogical#synchronous-replication)\n- [pglogical.use_spi](https://github.com/2ndQuadrant/pglogical#configuration-options)\n- [shared_buffers](https://www.postgresql.org/docs/16/runtime-config-resource.html#GUC-SHARED-BUFFERS)\n- [track_activity_query_size](https://www.postgresql.org/docs/16/runtime-config-statistics.html#GUC-TRACK-ACTIVITY-QUERY-SIZE)\n- [track_commit_timestamp](https://www.postgresql.org/docs/16/runtime-config-replication.html#GUC-TRACK-COMMIT-TIMESTAMP)\n- [wal_buffers](https://www.postgresql.org/docs/16/runtime-config-wal.html#GUC-WAL-BUFFERS)"]]