Select a documentation version: <button class="button button-with-icon cloud-select-dropdown__button button-primary" aria-haspopup="true">17.5.0</button>

- [Current (18.4.0)](https://docs.cloud.google.com/alloydb/omni/kubernetes/current/docs/reference/alloydb-flags.md.txt)
- [18.4.0](https://docs.cloud.google.com/alloydb/omni/kubernetes/18.4.0/docs/reference/alloydb-flags.md.txt)
- [18.3.0](https://docs.cloud.google.com/alloydb/omni/kubernetes/18.3.0/docs/reference/alloydb-flags.md.txt)
- [18.1.0](https://docs.cloud.google.com/alloydb/omni/kubernetes/18.1.0/docs/reference/alloydb-flags.md.txt)
- [17.10.0](https://docs.cloud.google.com/alloydb/omni/kubernetes/17.10.0/docs/reference/alloydb-flags.md.txt)
- [17.9.0](https://docs.cloud.google.com/alloydb/omni/kubernetes/17.9.0/docs/reference/alloydb-flags.md.txt)
- [17.7.0](https://docs.cloud.google.com/alloydb/omni/kubernetes/17.7.0/docs/reference/alloydb-flags.md.txt)
- [17.5.0](https://docs.cloud.google.com/alloydb/omni/kubernetes/17.5.0/docs/reference/alloydb-flags.md.txt)
- [16.14.0](https://docs.cloud.google.com/alloydb/omni/kubernetes/16.14.0/docs/reference/alloydb-flags.md.txt)
- [16.13.0](https://docs.cloud.google.com/alloydb/omni/kubernetes/16.13.0/docs/reference/alloydb-flags.md.txt)
- [16.11.0](https://docs.cloud.google.com/alloydb/omni/kubernetes/16.11.0/docs/reference/alloydb-flags.md.txt)
- [16.9.0](https://docs.cloud.google.com/alloydb/omni/kubernetes/16.9.0/docs/reference/alloydb-flags.md.txt)
- [16.8.0](https://docs.cloud.google.com/alloydb/omni/kubernetes/16.8.0/docs/reference/alloydb-flags.md.txt)
- [16.3.0](https://docs.cloud.google.com/alloydb/omni/kubernetes/16.3.0/docs/reference/alloydb-flags.md.txt)
- [15.18.0](https://docs.cloud.google.com/alloydb/omni/kubernetes/15.18.0/docs/reference/alloydb-flags.md.txt)
- [15.17.0](https://docs.cloud.google.com/alloydb/omni/kubernetes/15.17.0/docs/reference/alloydb-flags.md.txt)
- [15.15.0](https://docs.cloud.google.com/alloydb/omni/kubernetes/15.15.0/docs/reference/alloydb-flags.md.txt)
- [15.13.0](https://docs.cloud.google.com/alloydb/omni/kubernetes/15.13.0/docs/reference/alloydb-flags.md.txt)
- [15.12.0](https://docs.cloud.google.com/alloydb/omni/kubernetes/15.12.0/docs/reference/alloydb-flags.md.txt)
- [15.7.1](https://docs.cloud.google.com/alloydb/omni/kubernetes/15.7.1/docs/reference/alloydb-flags.md.txt)
- [15.7.0](https://docs.cloud.google.com/alloydb/omni/kubernetes/15.7.0/docs/reference/alloydb-flags.md.txt)

<br />


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](https://docs.cloud.google.com/alloydb/omni/docs/reference/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.audit_log_line_prefix

|---|---|
| Type | `string` |
| Default | `"%m [%p]: [%l-1] db=%d,user=%u` |
| Instance restarts | Yes |

Controls information prefixed to each audit log line. If left blank, then no
prefix is used.

### alloydb.enable_pgaudit

|---|---|
| Type | `boolean` |
| Default | `off` |
| Instance restarts | Yes |

Controls the availability of the `pgaudit` extension in an AlloyDB
instance. Set the parameter to `on` and restart the instance. Then add the
`pgaudit` extension to individual databases in the instance by using the `CREATE
EXTENSION` command.

The [`pgaudit`](https://www.pgaudit.org/) extension provides detailed session
and object audit logging using the standard logging facility provided by
PostgreSQL.

### alloydb.iam_authentication

|---|---|
| Type | `boolean` |
| Default | `off` |
| Instance restarts | Yes |

Enables the use of Identity and Access Management (Identity and Access Management (IAM)) authentication with
an AlloyDB instance.

### alloydb.logical_decoding

|---|---|
| Type | `boolean` |
| Default | `off` |
| Instance restarts | Yes |

Enables the PostgreSQL logical decoding infrastructure in
an AlloyDB instance.

[Logical decoding](https://www.postgresql.org/docs/17/logicaldecoding.html) provides the
infrastructure necessary to stream data modifications to external consumers.

> [!NOTE]
> **Note:** An automatic restart does not occur when you modify this parameter, and a manual restart of the database cluster is required for the change to take effect.

### alloydb.log_throttling_window

|---|---|
| Type | `integer` |
| Default | `0` |
| Instance restarts | No |

Controls whether AlloyDB records duplicate log messages
received during a specified time window.

If set to a value greater than `0`, then AlloyDB starts a
timer that many seconds long whenever it records a log message. If
AlloyDB receives the identical log message before the timer
expires, it does not record the message. After the timer expires,
AlloyDB appends a count of any skipped messages to the
next occurrence of the same log message that it records.

If set to `0`, then AlloyDB records all duplicate log
messages.

### alloydb.promote_cancel_to_terminate

|---|---|
| Type | `boolean` |
| Default | `off` |
| Instance restarts | No |

If set to `true`, then any query cancellation requests due to issues such as lock timeouts, statement timeouts, and recovery (replay) conflicts that AlloyDB encounters, are promoted to forced backend termination requests.

By promoting the cancellation requests, AlloyDB helps prevent stuck backends from blocking log replay and other backends.

### alloydb.pg_shadow_select_role

|---|---|
| Type | `string` |
| Default | An empty string |
| Instance restarts | No |

Name of the PostgreSQL role that is to be used to grant permission to query the
`pg_shadow` view.

### alloydb_password

|---|---|
| Type | `string` |
| Default | An empty string |
| Instance restarts | No |

Provides functions to set and manage password policies for
AlloyDB Omni. If your application's database users authenticate with
AlloyDB Omni using the built-in, password-based method, then you can
make authentication more secure by enforcing strong passwords.

For more information, see [Manage built-in authentication using password
policies](https://docs.cloud.google.com/alloydb/omni/docs/manage-password-policy).

### alloydb_scann

|---|---|
| Type | `string` |
| Default | An empty string |
| Instance restarts | No |

Provides functions that enable AlloyDB Omni to handle vector search
workloads with high performance and efficiency.

For more information, see [Create indexes and query vectors](https://docs.cloud.google.com/alloydb/omni/kubernetes/17.5.0/docs/ai/store-index-query-vectors.md.txt?resource=scann).

### alloydb_ai_nl

|---|---|
| Type | `string` |
| Default | An empty string |
| Instance restarts | No |

Provides functions that let you securely query AlloyDB using natural language.
The extension works together with the parameterized_views\` extension that
enforces a security layer for your data.

For more information, see [Query your database using natural language](https://docs.cloud.google.com/alloydb/omni/kubernetes/17.5.0/docs/ai/use-psvs).

### parameterized_views

|---|---|
| Type | `string` |
| Default | An empty string |
| Instance restarts | No |

Provides functions that add a security layer when natural language queries are
translated to SQL queries. This extension works together with the
`alloydb_ai_nl` extension.

For more information, see [Query your database using natural language](https://docs.cloud.google.com/alloydb/omni/kubernetes/17.5.0/docs/ai/use-psvs).