Anda menggunakan flag database untuk banyak operasi, termasuk menyesuaikan parameter PostgreSQL, menyesuaikan opsi, serta mengonfigurasi dan melakukan tuning pada instance.
Kolom lain dalam tabel berisi informasi tambahan tentang setiap tanda AlloyDB Omni:
Klik nama tanda untuk melihat petunjuk penggunaannya.
Kolom Nilai default menampilkan nilai yang ditetapkan AlloyDB Omni untuk tanda ini di instance baru, kecuali jika Anda menentukan nilai yang berbeda saat membuat instance.
Default standar menunjukkan bahwa tanda memiliki nilai default yang tidak ditetapkan oleh AlloyDB Omni. Untuk mempelajari lebih lanjut, klik nama negara.
Di kolom Mulai ulang diperlukan, Ya menunjukkan bahwa
Anda perlu memulai ulang AlloyDB Omni saat menetapkan, menghapus, atau
mengubah tanda pada instance. Nilai flag tetap ada untuk
instance hingga Anda mengubahnya lagi.
Di kolom Replica restrictions, Yes menunjukkan batasan berikut tentang cara Anda dapat menggunakan tanda:
Sebelum menyetel flag ini di instance utama cluster Anda, tetapkan
flag di setiap instance replika cluster Anda.
Jika instance utama menetapkan tanda ini, nilai tanda ini pada instance replika mana pun harus sama dengan atau lebih besar daripada nilai tanda ini pada instance utama.
Flag PostgreSQL standar yang memerlukan mulai ulang
Flag PostgreSQL standar berikut memerlukan mulai ulang AlloyDB Omni saat Anda menyetel, menghapus, atau mengubah flag pada instance. Nilai flag tetap ada untuk instance hingga Anda mengubahnya lagi.
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Sulit dipahami","hardToUnderstand","thumb-down"],["Informasi atau kode contoh salah","incorrectInformationOrSampleCode","thumb-down"],["Informasi/contoh yang saya butuhkan tidak ada","missingTheInformationSamplesINeed","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 2025-09-03 UTC."],[[["\u003cp\u003eThis page details the database flags supported by AlloyDB Omni, which are used for operations like adjusting PostgreSQL parameters, configuring options, 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; some flags have a "Standard default," indicating a value not set by AlloyDB Omni.\u003c/p\u003e\n"],["\u003cp\u003eThe "Restart required" column indicates whether AlloyDB Omni needs to be restarted after setting, removing, or modifying a flag, and if a flag requires a restart, it persists until modified.\u003c/p\u003e\n"],["\u003cp\u003eThe "Replica restrictions" column specifies whether a flag must be set on all replica instances before being set on the primary, or if the value on the replica must be equal to or greater than the primary instance's value.\u003c/p\u003e\n"],["\u003cp\u003eClicking on a flag name in the table provides more detailed information about its usage and specific configurations.\u003c/p\u003e\n"]]],[],null,["# Supported database flags\n\nSelect a documentation version: 15.7.1keyboard_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/15/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/15.7.1/docs/configure-database-flags).\n\nAlloyDB Omni flags\n------------------\n\nThe table's other columns contain additional information\nabout each AlloyDB Omni flag:\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/15/runtime-config-autovacuum.html#GUC-AUTOVACUUM-FREEZE-MAX-AGE)\n- [autovacuum_max_workers](https://www.postgresql.org/docs/15/runtime-config-autovacuum.html#GUC-AUTOVACUUM-MAX-WORKERS)\n- [autovacuum_multixact_freeze_max_age](https://www.postgresql.org/docs/15/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/15/runtime-config-connection.html#GUC-MAX-CONNECTIONS)\n- [max_locks_per_transaction](https://www.postgresql.org/docs/15/runtime-config-locks.html#GUC-MAX-LOCKS-PER-TRANSACTION)\n- [max_logical_replication_workers](https://www.postgresql.org/docs/15/runtime-config-replication.html#GUC-MAX-LOGICAL-REPLICATION-WORKERS)\n- [max_pred_locks_per_page](https://www.postgresql.org/docs/15/runtime-config-locks.html#GUC-MAX-PRED-LOCKS-PER-PAGE)\n- [max_pred_locks_per_relation](https://www.postgresql.org/docs/15/runtime-config-locks.html#GUC-MAX-PRED-LOCKS-PER-RELATION)\n- [max_pred_locks_per_transaction](https://www.postgresql.org/docs/15/runtime-config-locks.html#GUC-MAX-PRED-LOCKS-PER-TRANSACTION)\n- [max_prepared_transactions](https://www.postgresql.org/docs/15/runtime-config-resource.html#GUC-MAX-PREPARED-TRANSACTIONS)\n- [max_replication_slots](https://www.postgresql.org/docs/15/runtime-config-replication.html#GUC-MAX-REPLICATION-SLOTS)\n- [max_wal_senders](https://www.postgresql.org/docs/15/runtime-config-replication.html#GUC-MAX-WAL-SENDERS)\n- [max_worker_processes](https://www.postgresql.org/docs/15/runtime-config-resource.html#GUC-MAX-WORKER-PROCESSES)\n- [old_snapshot_threshold](https://www.postgresql.org/docs/15/runtime-config-resource.html#GUC-OLD-SNAPSHOT-THRESHOLD)\n- [pg_stat_statements.max](https://www.postgresql.org/docs/15/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/15/runtime-config-resource.html#GUC-SHARED-BUFFERS)\n- [track_activity_query_size](https://www.postgresql.org/docs/15/runtime-config-statistics.html#GUC-TRACK-ACTIVITY-QUERY-SIZE)\n- [track_commit_timestamp](https://www.postgresql.org/docs/15/runtime-config-replication.html#GUC-TRACK-COMMIT-TIMESTAMP)\n- [wal_buffers](https://www.postgresql.org/docs/15/runtime-config-wal.html#GUC-WAL-BUFFERS)"]]