For more information about how to use each flag listed in the following
table, click the name of the flag.
The table's other columns contain additional information
about each flag:
The Default value column displays the value that
AlloyDB Omni sets for this flag in a new instance, unless you specify a different value when creating the instance.
Standard default indicates that the flag has a default value that's not
set by AlloyDB Omni. To learn more, click the flag's name.
In the Restart required column, Yes indicates that
you need to restart 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.
In the Replica restrictions column, Yes indicates the following
restrictions on how you can use the flag:
Before setting this flag on your cluster's primary instance, set
the flag on each of your cluster's replica instances.
If the primary instance has this flag set, then the value of this
flag on any replica instance must be equal to or greater
than the primary instance's value for this flag.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-25 UTC."],[[["\u003cp\u003eThis page provides a comprehensive list of database flags supported by AlloyDB Omni, which are crucial for various operations like adjusting parameters and tuning instances.\u003c/p\u003e\n"],["\u003cp\u003eEach flag's default value, whether it's set by AlloyDB Omni or is a standard default, is indicated in the table, and clicking on the flag's name provides detailed information.\u003c/p\u003e\n"],["\u003cp\u003eThe table indicates if a restart of AlloyDB Omni is required after modifying a flag, ensuring the change is applied effectively, and the flag's value will persist until it is changed again.\u003c/p\u003e\n"],["\u003cp\u003eThe "Replica restrictions" column identifies flags that require specific configurations on replica instances before or when they are set on the primary instance, such as ensuring replica values are equal to or greater than the primary.\u003c/p\u003e\n"],["\u003cp\u003eThe database flags listed are categorized and organized by their respective purposes, such as columnar engine flags, index-advisor flags, password policy flags and more.\u003c/p\u003e\n"]]],[],null,["# Supported database flags\n\nSelect a documentation version: 15.7.0keyboard_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\nThis page lists the database flags that AlloyDB Omni supports.\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.0/docs/configure-database-flags).\n\nFor more information about how to use each flag listed in the following\ntable, click the name of the flag.\n\nThe table's other columns contain additional information\nabout each flag:\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)"]]