Configuration

This section guides you through changing your PostgreSQL cluster configuration.

Console (UI)

Click the name of your cluster on the Clusters page, then open the Parameters tab to view and edit cluster settings.

Cluster

View and modify general cluster settings such as synchronous replication, disk size, IOPS, throughput, networking options, and the index maintenance.

Postgres

Configure PostgreSQL-specific runtime parameters (for example, autovacuum settings, WAL and checkpoint behavior, memory-related parameters). Use the search and filters to find parameters and review which settings require a restart.

HBA

Manage PostgreSQL host-based authentication (HBA) rules. Add, edit, or remove rules that control which hosts and users can connect and which authentication methods are enforced.

Connection Pools

Configure connection pool settings and individual pools. Set pool counts, pool modes, max client connections, and per-pool parameters to control how client connections are multiplexed.

YAML editor

The YAML editor allows you to specify any parameters that were previously available only in command-line mode. Designed for experienced users.

To open the editor, click the YAML icon in the top-right corner of the cluster page.

info

To use the YAML editor, go to the Settings page and turn on “Enable expert mode” and “Enable YAML editor”.

Command line

To change the cluster configuration using the automation image:

1. Modify the desired parameters (for example, postgresql_parameters).

info

Refer to the default values; override them as needed using group_vars, host_vars, or directly in the inventory file.

2. Run the config_pgcluster.yml playbook to apply the changes.

Example:

docker run --rm -it \
  -e ANSIBLE_SSH_ARGS="-F none" \
  -e ANSIBLE_INVENTORY=/project/inventory \
  -v $PWD:/project \
  -v $HOME/.ssh:/root/.ssh \
  autobase/automation:2.9.0 \
    ansible-playbook config_pgcluster.yml

note

Optionally, set pending_restart: true to automatically restart PostgreSQL if the parameter change requires a restart.

tip

You can use GitOps and CI/CD pipelines to manage PostgreSQL configuration in a fully automated and reproducible way.