5 Configuration Parameters
Added, modified, removed, and default-value changes for configuration parameters.
PDF page 55
In PostgreSQL 13 the following parameters have been changed.
3.3.1 Added parameters
The following parameters have been added.
| Parameter name | Description (context) | Default Val |
|---|---|---|
| autovacuum_vacuum_ | Percentage of INSERT records for which automatic | 0.2 |
| insert_scale_factor | VACUUM is executed (sighup). | |
| autovacuum_vacuum_insert_threshold | Number of INSERT records for which automatic VACUUM is executed (sighup). | 1000 |
| backtrace_functions | List of function names that output backtrace when an error occurs (superuser). | '' |
| enable_incremental_sort | Enable incremental sorting (user). | on |
| hash_mem_multiplier | Used to compute the maximum amount of memory that hash-based operations can use (user). | 1 |
| ignore_invalid_pages | Ignore invalid page references during recovery (postmaster) . | off |
| log_min_duration_sample | Time to output SQL statement log by sampling (superuser) . | -1 |
| log_parameter_max_length | Bind parameter value in the non-error statement logging messages are trimmed to setting value (superuser). | -1 |
| log_parameter_max_length_on_error | Bind parameter value in the error statement logging messages are trimmed to setting value (user). | 0 |
| log_statement_sample_rate | SQL statement log output rate by sampling (superuser) | 1.0 |
| logical_decoding_work_mem | Work memory for decoding for the logical replication environment (user). | 64MB |
| maintenance_io_concurrency | Number of I/O concurrent executions used for maintenance (user). | 10 |
| max_slot_wal_keep_size | The maximum MB size of WAL is held by the replication slot (sighup). | -1 |
| wal_receiver_create_temp_slot | Whether the wal receiver process creates a temporary replication slot (sighup). | off |
| wal_skip_threshold | Write the interval at which fsync is executed when wal_level is ‘minimal’ (user). | 2MB |
PDF page 56
Output backtrace
In the parameter backtrace_functions, specify the name of the function that performs trace output when an error occurs. The specified function is not the SQL function, but the function name in the source code.
PDF page 57
PDF page 58
3.3.2 Changed parameters
The setting range and options were changed for the following configuration parameters.
| Parameter name | Changes |
|---|---|
| allow_system_table_mods | The context changed from postmaster to superuser. |
| effective_io_concurrency | Changed to use directly specified value instead of using calculated value by the internal logic. |
| log_line_prefix | Backend type (%b) has been added. |
| log_min_duration_statement | The short_desc column value in the pg_settings view has changed. |
| max_files_per_process | The minimum value has been changed from 25 to 64. |
| primary_conninfo | Context changed from postmaster to sighup. |
| primary_slot_name | Context changed from postmaster to sighup. |
| ssl_passphrase_command | Only SUPERUSER can be referenced. |
| track_activity_query_size | The maximum value has been changed from 102,400 to 1,048,576. |
| wal_keep_size | Changed name from wal_keep_segments. Units have been changed from number of the files to size. |
3.3.3 Parameters with default values changed
The following parameters have changed default values.
| Parametername | PostgreSQL12 | PostgreSQL13 | Note |
|---|---|---|---|
| server_version | 12.4 | 13.0 | |
| server_version_num | 120004 | 130000 | |
| ssl_min_protocol_version | TLSv1 | TLSv1.2 |