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

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

<br />

To configure a database parameter for AlloyDB Omni, you can update [Grand Unified Configuration (GUC) parameters](https://www.postgresql.org/docs/current/config-setting.html) in the `postgresql.conf` file for environments running AlloyDB Omni on a VM. For a list of supported flags, see [Supported database flags](https://docs.cloud.google.com/alloydb/omni/containers/18.4.0/docs/reference/database-flags.md.txt).

## Update a parameter in containerized AlloyDB Omni

In an AlloyDB Omni running on a VM, you can update a parameter by editing the `postgresql.conf` file as follows:

1. Locate the `postgresql.conf` configuration file for your installation of
   AlloyDB Omni.

2. Use a text editor to add or update a database flag in `postgresql.conf`.

   For example, to
   [enforce password expiration](https://docs.cloud.google.com/alloydb/omni/containers/18.4.0/docs/manage-password-policy.md.txt#enforce-password-expiration),
   set the following flag in the `postgresql.conf` file:

   ```bash
   password.enforce_expiration = ON
   ```
3. After your database flags are added or edited, reload the `postgresql.conf`
   file for the changes to take effect. For example, if you
   [installed AlloyDB Omni using Docker](https://docs.cloud.google.com/alloydb/omni/containers/18.4.0/docs/quickstart.md.txt#install-using-docker),
   run the following to restart your Docker instance and reload
   `postgresql.conf`:

   ```bash
   docker restart CONTAINER-NAME
   ```

For more
information, see
[Setting parameters](https://www.postgresql.org/docs/current/config-setting.html)
in PostgreSQL documentation.

## Audit database parameters using the web UI

You can audit active database flags and identify customized parameters that differ from default engine values using the **Database flags** page in the AlloyDB Omni web user interface.

To audit database parameters in the web UI, complete the following steps:

1. [Connect to the web UI](https://docs.cloud.google.com/alloydb/omni/containers/18.4.0/docs/connect-web-ui) and select your cluster.
2. In the navigation menu, click **Database flags**.
3. Use the following controls to search and filter parameters:
   - **Search for flags** : Enter a keyword (for example, `max`) to filter parameters by name.
   - **Show modified flags** : Select this checkbox to display only parameters whose active values differ from their default engine values. Customized values are also highlighted in yellow in the **Current value** column.
   - **Collapse all** or **Expand all** : Collapse or expand the parameter category groups (such as **Google AlloyDB Options** , **Client Connection Defaults / Locale and Formatting** , **Client Connection Defaults / Other Defaults** , and **Client Connection Defaults / Shared Library Preloading**).
4. Review the parameter table columns within each category group:
   - **Setting**: The name of the database parameter.
   - **Type** : The data type of the parameter (for example, `INTEGER`).
   - **Current value**: The active value of the parameter on the instance (highlighted in yellow if modified from the default).
   - **Default value**: The default engine value for the parameter.
   - **Restart required** : Indicates whether modifying the parameter requires a database restart (`true` or `false`).
   - **Source** : The configuration source of the current value (for example, `default`).