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

PostgreSQL settings for 1C

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 selected to ensure high cluster performance and vary depending on the cluster configuration and PostgreSQL version.

If the automatic values are not suitable for your application, set your own values at cluster creation or change settings in an already created cluster.

For your information

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

View list of settings⁠

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

You can view a list of settings that can be changed by cluster creation or customization.

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

  1. In control panel go to Cloud platform → Databases.
  2. Open the cluster page → tab Settings.
  3. In the block DBMS settings displays the previously changed settings — name and value.

Change settings⁠

For your information

Changing some parameters in the settings causes the databases in the cluster to reboot — the cluster may be unavailable during this time. Take a look list of these settings.

  1. In control panel go to Cloud platform → Databases.
  2. Open the cluster page → tab Settings.
  3. In the block DBMS settings click Modify 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_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.

Settings when scaling a cluster⁠

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

When the cluster is scaled up and moves to status ACTIVEyou'll be able to set the 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.