Skip to content

12 Change of Configuration Parameters

Source chapter 3.10 for PostgreSQL 10.
Beta 1Source pages: PDF 81-85Original PDF on GitHub

PDF page 81

In PostgreSQL 10 the following parameters have been changed.

3.10.1 Added parameters

The following parameters have been added.

Parameter nameDescription (context)Default
enable_gathermergeEnable execution plan Gather Merge (user)on
max_parallel_workersMaximum number of parallel worker process (user)8
max_sync_workers_per_subscriptionMaximum number of synchronous workers for SUBSCRIPTION (sighup)2
wal_consistency_checkingCheck the consistency of WAL on the standby instance (superuser)-
max_logical_replication_workersMaximum number of Logical Replication worker process (postmaster)4
max_pred_locks_per_relationMaximum number of pages that can be Predicate- Lock before locking the entire relation (sighup)-2
max_pred_locks_per_pageMaximum number of records that can be Predicate-Lock before locking the entire page (sighup)2
min_parallel_table_scan_sizeMinimum table size at which Parallel table scan are considered (user)8MB
min_parallel_index_scan_sizeMinimum table size at which Parallel index scan are considered (user)512kB
Table 26 Added parameters
Parameter max_parallel_workers

Specifies the maximum number of parallel query worker processes that can run concurrently in the instances. The default value is 8. In the old version, the max_worker_processes parameter was the upper limit. If this value is set to 0, the parallel query is invalidated.

Parameter max_logical_replication_workers

Specifies the maximum value of the Logical Replication Worker processes to be started for each SUBSCRIPTION. Even if the value of this parameter is less than the required value, CREATE

PDF page 82

SUBSCRIPTION statement will not fail. The following logs are periodically output when replication starts.

Example 91 Lack max_logical_replication_workers parameters
WARNING:  out of logical replication worker slots
HINT:  You might need to increase max_logical_replication_workers.
Parameter wal_consistency_checking

This parameter is used for bug checking of the WAL re-execution program in the replication environment. For the parameter, specify the object type to be checked with a comma (,) delimiter. The following values are available: all, hash, heap, heap 2, btree, gin, gist, sequence, spgist, brin, generic.

Parameter max_pred_locks_per_page

Specifies the maximum number of tuple locks to transition to page lock.

Parameter max_pred_locks_per_relation

Specifies the maximum number of page locks to transition to relation lock.

3.10.2 Changed parameters

The setting range and options were changed for the following configuration parameters.

PDF page 83

sslchanged to sighup
ssl_ca_fileThe value of the context column has been changed to sighup
ssl_cert_fileThe value of the context column has been changed to sighup
ssl_ciphersThe value of the context column has been changed to sighup
ssl_crl_fileThe value of the context column has been changed to sighup
ssl_ecdh_curveThe value of the context column has been changed to sighup
ssl_key_fileThe value of the context column has been changed to sighup
ssl_prefer_server_ciphersThe value of the context column has been changed to sighup
bgwriter_lru_maxpagesThe value of max_val column was changed to INT_MAX / 2
archive_timeoutThe value of the short_desc column has changed
server_version_numThe value of max_val / min_val column was changed to 100000
password_encryptionThe value of the vartype was changed to enum. “md5” or “scram-sha- 256” can specified. “on” is a alias for “md5”
max_wal_sizeThe value of the unit column has been changed to 1MB
min_wal_sizeThe value of the unit column has been changed to 1MB
Table 27 Changed configuration parameters (from pg_settings catalog)

Parameter name Changes

3.10.3 Parameters with default values changed

The default values of the following configuration parameters have been changed.

Parameter namePostgreSQL 9.6PostgreSQL 10
hot_standbyoffon
log_line_prefix''%m [%p]
max_parallel_workers_per_gather02
max_replication_slots010
max_wal_senders010
password_encryptiononmd5
server_version9.6.310beta1
server_version_num90603100000
wal_levelminimalreplica
log_directorypg_loglog
Table 28 Parameters with default values changed

PDF page 84

Parameter log_line_prefix

The parameter default value has been changed.

Example 92 Parameter log_line_prefix default
postgres=# SHOW log_line_prefix ;
 log_line_prefix
-----------------
 %m [%p]
(1 row)
$ tail -1 data/log/postgresql-2017-05-20_093448.log
2017-05-20 09:34:48.617 JST [12187] LOG:  autovacuum launcher started

3.10.4 Deprecated parameters

The following parameters are deprecated.

Parameter nameAlternative value
min_parallel_relation_sizesql_inheritanceChanged to min_parallel_table_scan_size None (same as ‘on’)
Table 29 Deprecated parameters

3.10.5 New function of authentication method

The following changes were made to the pg_hba.conf file.

Specify the RADIUS server

The specification of the RADIUS server necessary for RADIUS authentication changed from “radiusserver” to “radiusservers”. Multiple servers separated by commas can be specified.

Added SCRAM authentication

Scram-sha-256 can be specified for the authentication method in pg_hba.conf. This is an implementation of SCRAM-SHA-256 as specified in RFC 5802 and 7677. Scram-sha-256 can also be specified for configuration parameter password_encryption.

PDF page 85

3.10.6 Default value of authentication setting

The replication related default value contained in the pg_hba.conf file has been changed. By default, the local connection is set to the “trust” setting.

Example 93 Default setting of pg_hba.conf file
# Allow replication connections from localhost, by a user with the
# replication privilege.
local   replication     all                                     trust
host    replication     all             127.0.0.1/32            trust
host    replication     all             ::1/128                 trust

3.10.7 Other parameter change

The parameter recovery_target_lsn related to “Point In Time Recovery” has been added to the recovery.conf file. For this parameter, specify the recovery complete LSN.