Skip to main content
PostgreSQL Settings for 1C
Last update:

PostgreSQL Settings for 1C

PostgreSQL settings affect the performance of the database cluster. When creating a PostgreSQL database cluster, the values for all settings are set automatically. The values are selected to ensure high performance of the cluster, they differ 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 changing settings values only when necessary — improperly chosen values can degrade cluster performance. When scaling the cluster, some settings are automatically replaced with valid values.

View settings-list

See the detailed description of settings in the official PostgreSQL documentation.

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

If you 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 settings in the settings entails rebooting the databases in the cluster — the cluster may be unavailable during this time. See list of these settings.

  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. Click Save

List of settings that require a reboot

  • autovacuum_freeze_max_age;
  • autovacuum_max_workers;
  • autovacuum_multixact_freeze_max_max_age;
  • max_files_per_process;
  • max/predicted/locks/per_transaction;
  • max\prepared_transactions;
  • old_snapshot\threshold;
  • track\activity\query_size;
  • max_connections;
  • max_locks_per_transaction;
  • max_worker/processes;
  • shared/buffers.


Any DBMS parameter has limits on its allowable values. When cluster scaling-up (configuration change), some settings are automatically changed to acceptable values so that the cluster can work.

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

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.