This page describes the database flags that AlloyDB for PostgreSQL uses to enable and manage various service features unique to AlloyDB. For a list of all database flags that AlloyDB supports, see Supported database flags.
Flags marked with Instance restarts mean 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.
alloydb_ai_nl.enabled
| Type | boolean |
| Default | off |
| Instance restarts | Yes |
Controls whether the AlloyDB AI natural language features are enabled.
alloydb.enable_anon
| Type | boolean |
| Default | off |
| Instance restarts | Yes |
Controls the availability of the anon (PostgreSQL Anonymizer) extension in an AlloyDB instance. Set this parameter to on and restart the instance. Then, add the anon extension to individual databases in the instance by using the CREATE EXTENSION command. Before you can install the anon extension, you must first install the pgcrypto extension.
The anon extension lets you hide or replace personally identifiable information (PII) or commercially sensitive data within your database.
alloydb.enable_auto_explain
| Type | boolean |
| Default | off |
| Instance restarts | Yes |
Controls the availability of the auto_explain extension in
an AlloyDB instance. Set the parameter to on and restart the
instance.
The auto_explain extension enables
automatic logging of execution plans of slow statements, for troubleshooting and
more. It provides an automated way to perform the functionality of the EXPLAIN
command.
alloydb.enable_cache_aware_costing
| Type | boolean |
| Default | off |
| Instance restarts | No |
Lets the AlloyDB query planner adjust the estimated IO cost of index scans based on how many index and table pages may be already available in the shared buffer when execution starts.
For more information, see