Supported database flags

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

AlloyDB flag
Default value
Instance restarts
Read pool restrictions
An empty string
No
No
allow_alter_system (PostgreSQL 17)
on
No
No
Standard default
No
No
Standard default
No
No
Standard default
No
No
Standard default
No
No
Standard default
No
No
Standard default
No
No
Standard default
No
No
Standard default
No
No
Standard default
No
No
Standard default
No
No
Standard default
No
No
Standard default
No
No
Standard default
No
No
Standard default
No
No
Standard default
No
No
Standard default
Yes
No
Standard default
Yes
No
Standard default
Yes
No
Standard default
No
No
Standard default
No
No
Standard default
No
No
Standard default
No
No
Standard default
No
No
Standard default
No
No
Standard default
No
No
Standard default
No
No
Standard default
No
No
Standard default
No
No
Standard default
No
No
commit_timestamp_buffers (PostgreSQL 17)
0
Yes
No
Standard default
No
No
Standard default
No
No
Standard default
No
No
Standard default
No
No
createrole_self_grant (PostgreSQL 16)
-
No
No
Standard default
Yes
No
Standard default
No
No
Standard default
Yes
No
Standard default
Yes
No
Standard default
Yes
No
Standard default
No
No
Standard default
No
No
debug_io_direct (PostgreSQL 16)
-
No
No
buffered
No
No
debug_parallel_query (PostgreSQL 16)
off
No
No
Standard default
No
No
Standard default
No
No
Standard default
No
No
Standard default
No
No
80% of instance RAM
No
No
Standard default
No
No
on
No
No
Standard default
No
No
Standard default
No
No
Standard default
No
No
Standard default
No
No
Standard default
No
No
Standard default
No
No
Standard default
No
No
on
No
No
Standard default
No
No
Standard default
No
No
Standard default
No
No
event_triggers (PostgreSQL 17)
true
No
Yes
Standard default
No
No
Standard default
No
No
Standard default
No
No
Standard default
No
No
Standard default
No
No
Standard default
No
No
Standard default
No
No
Standard default
No
No
Standard default
No
No
Standard default
No
No
Standard default
No
No
30% of instance RAM
Yes
No
An empty string
No
No
google_ml_integration.enable_faster_embedding_generation
off
No
No
gss_accept_delegation (PostgreSQL 16)
off
No
No
icu_validation_level (PostgreSQL 16)
warning
No
No
Standard default
No
No
Standard default
No
No
86,400,000
No
No
Standard default
No
No
Standard default
No
No
Standard default
No
No
Standard default
No
No
Standard default
No
No
Standard default
The log_duration=on setting might increase log volume under a heavy workload and cause higher query latencies.
No
No
Standard default
No
No
Standard default
No
No
Standard default
No
No
Standard default
No
No
Standard default
No
No
Standard default
No
No
Standard default
No
No
Standard default
No
No
Standard default
No
No
Standard default
No
No
Standard default
No
No
Standard default
The log_statement=all setting might increase log volume under a heavy workload and cause higher query latencies.
No
No
Standard default
No
No
0
No
No
Standard default
No
No
1000
Yes
Yes
Standard default
Yes
Yes
Standard default
Yes
No
max_notify_queue_pages (PostgreSQL 17)
1048576
Yes
Yes
Standard default
No
No
The instance CPU count or 8 , whichever is greater
No
No
Half of the instance CPU count or 2 , whichever is greater
No
No
Standard default
Yes
No
Standard default
Yes
No
Standard default
Yes
No
Standard default
Yes
Yes
Standard default
No
No
Standard default
No
No
Standard default
No
No
50
Yes
Yes
1504
No
No
Standard default
No
No
multixact_member_buffers (PostgreSQL 17)
32
Yes
No
multixact_offset_buffers (PostgreSQL 17)
32
Yes
No
notify_buffers (PostgreSQL 17)
16
Yes
No
Standard default
No
No
86400
No
No
Standard default
No
No
Standard default
No
No
Standard default
No
No
Standard default
No
No
Standard default
No
No
Standard default
No
No
Standard default
No
No
Standard default
No
No
Standard default
Yes
No
Standard default
No
No
Standard default
No
No
Standard default
No
No
Standard default
No
No
Standard default
No
No
Standard default
No
No
Standard default
No
No
Standard default
No
No
Standard default
No
No
Standard default
No
No
Standard default
No
No
Standard default
Yes
No
Standard default
No
No
Standard default
No
No
Standard default
No
No
Standard default
Yes
No
Standard default
Yes
No
Standard default
No
No
Standard default
No
No
reserved_connections (PostgreSQL 16)
0
Yes
No
scram_iterations (PostgreSQL 16)
4096
No
No
send_abort_for_crash (PostgreSQL 16)
off
No
No
send_abort_for_kill (PostgreSQL 16)
off
No
No
serializable_buffers (PostgreSQL 17)
32
Yes
No
80% of instance memory
Yes
No
Standard default
No
No
Standard default
No
No
Standard default
No
No
Standard default
No
No
Default value is 1
No
No
Default value is 1 . Set to any value between 1 and 2147483647
No
No
Standard default
No
No
Standard default
No
No
subtransaction_buffers (PostgreSQL 17)
0
Yes
No
summarize_wal (PostgreSQL 17)
off
No
Yes
sync_replication_slots (PostgreSQL 17)
off
No
Yes
Standard default
No
No
off
No
Yes
Standard default
No
No
Standard default
No
No
off
Yes
No
Standard default
No
No
Standard default
No
No
Standard default
No
No
Standard default
No
No
Standard default
Yes
No
Standard default
Yes
No
Standard default
No
No
Standard default
No
No
on
No
No
transaction_buffers (PostgreSQL 17)
0
Yes
No
transaction_timeout (PostgreSQL 17)
0
No
No
vacuum_buffer_usage_limit (PostgreSQL 16)
256
No
No
Standard default
No
No
Standard default
No
No
Standard default
No
No
Standard default
No
No
Standard default
No
No
Standard default
No
No
The default depends on the number of vCPUs, as shown in the following list:
  • < 8vCPU: 16MB (2048 8k buffers)
  • 8 vCPU: 128MB (16384 8k buffers)
  • 16 vCPU: 256MB (32768 8k buffers)
  • 32 vCPU: 512MB (65536 8k buffers)
  • 64 vCPU: 1GB (131072 8k buffers)
  • 96 vCPU: 1.5GB (196608 8k buffers)
  • 128 vCPU: 2GB (262144 8k buffers)
Yes
No
Standard default
No
No
Standard default
No
No
wal_summary_keep_time (PostgreSQL 17)
10 days
No
Yes
N MB , where N is either 4 or the number of instance vCPUs, whichever is greater
No
No
Design a Mobile Site
View Site in Mobile | Classic
Share by: