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 valuecolumn displays the value that AlloyDB sets for this flag in a new instance, unless you specify a different value when creating the instance. Standard defaultindicates that the flag has a default value that's not set by AlloyDB. To learn more, click the flag's name. 
-  In the Instance restartscolumn, Yesindicates 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 restrictionscolumn, Yesindicates 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. 
 
-  
A | C | D | E | F | G | H | I | J | L | M | P | R | S | T | V | W
The
log_duration=on 
setting might increase log volume under a heavy workload and cause higher query latencies.The
log_statement=all 
setting might increase log volume under a heavy workload and cause higher query latencies.
