Stay organized with collections Save and categorize content based on your preferences.
This page lists the database flags that AlloyDB for PostgreSQL supports.
You use database flags for many operations, including adjusting PostgreSQL parameters, adjusting options, and configuring and tuning instances.
For more information about setting database flags in AlloyDB, see Configure an instance's database flags.
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 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. To learn more, click the flag's name.
In the Instance restarts column, Yes indicates that AlloyDB restarts an instance whenever you set, remove, or modify this flag on that instance. The flag's value persists for the instance until you modify it again.
In the Read pool 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 read pool instances.
If the primary instance has this flag set, then the value of this flag on any read pool instance must be equal to or greater than the primary instance's value for this flag.
Preview — PostgreSQL 17
This feature is subject to the "Pre-GA Offerings Terms" in the General Service Terms section of the Service Specific Terms. Pre-GA features are available "as is" and might have limited support. For more information, see the launch stage descriptions.
A | C | D | E | F | G | H | I | J | L | M | O | P | R | S | T | V | W
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4