Skip to main content
PostgreSQL settings
Last update:

PostgreSQL settings

PostgreSQL settings affect the performance of the database cluster. When you create a PostgreSQL database cluster, the values for all settings are set automatically. The values are chosen to ensure high cluster performance and vary depending on the cluster configuration and PostgreSQL version.

If the automatic values are not suitable for your tasks, set your own values when creating a cluster or change settings in an already created cluster.

For your information

We recommend that you change the settings only when necessary — incorrect values can degrade cluster performance. When you scale the cluster, the values of some settings are automatically replaced with valid values.

View a list of settings

See the detailed description of settings in official PostgreSQL documentation.

You can view the list of settings available for change when creating a cluster or change-settings.

If you have changed settings, you can see a list of all changes.

  1. In Control Panel, go to Cloud PlatformDatabases.
  2. Open the cluster page → Settings tab.
  3. The DBMS Settings block displays the previously changed settings — name and value.

Change settings

For your information

Changing some parameters in the settings entails rebooting the databases in the cluster — the cluster may be unavailable during this time. These settings depend on the PostgreSQL version — check out their list.

  1. In Control Panel, go to Cloud PlatformDatabases.
  2. Open the cluster page → Settings tab.
  3. In the DBMS Settings block, click Change and specify the new values.
  4. Press Save

List of settings that require a reboot

  • autovacuum_freeze_max_age;
  • autovacuum_max_workers;
  • autovacuum_multixact_freeze_max_age;
  • max_files_per_process;
  • max_pred_locks_per_transaction;
  • max_prepared_transactions;
  • old_snapshot_threshold;
  • track_activity_query_size;
  • max_connections;
  • max_locks_per_transaction;
  • max_worker_processes;
  • shared_buffers (for all versions except PostgreSQL 11).

Settings when scaling a cluster

Any DBMS parameter has limits of acceptable values. When cluster scaling (reconfiguration), the values of some settings are automatically changed to valid values so that the cluster can run.

When the cluster is scaled and goes to ACTIVE status, you can set new values — change-settings.

A list of settings that change values when the cluster is scaled:

  • shared_buffers;
  • effective_cache_size;
  • maintenance_work_mem;
  • max_worker_processes;
  • max_parallel_workers;
  • autovacuum_max_workers;
  • vacuum_cost_limit;
  • max_parallel_workers_per_gather;
  • max_maintenance_workers.