From 873605688052868e68609502afab5389b79e2e49 Mon Sep 17 00:00:00 2001 From: Marcos Date: Wed, 14 May 2025 17:34:42 -0300 Subject: [PATCH] Trying to put some standard on default values of variables --- doc/src/sgml/config.sgml | 1559 +++++++++++++++++--------------------- 1 file changed, 687 insertions(+), 872 deletions(-) diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml index 23d2b1be424..aef2d9b14d3 100644 --- a/doc/src/sgml/config.sgml +++ b/doc/src/sgml/config.sgml @@ -518,7 +518,7 @@ include_dir 'conf.d' - data_directory (string) + data_directory (string) - has no default value data_directory configuration parameter @@ -532,45 +532,42 @@ include_dir 'conf.d' - config_file (string) + config_file (string) - default is postgresql.conf config_file configuration parameter - Specifies the main server configuration file - (customarily called postgresql.conf). + Specifies the main server configuration file. This parameter can only be set on the postgres command line. - hba_file (string) + hba_file (string) - default is pg_hba.conf hba_file configuration parameter - Specifies the configuration file for host-based authentication - (customarily called pg_hba.conf). + Specifies the configuration file for host-based authentication. This parameter can only be set at server start. - ident_file (string) + ident_file (string) - default is pg_ident.conf ident_file configuration parameter - Specifies the configuration file for user name mapping - (customarily called pg_ident.conf). + Specifies the configuration file for user name mapping. This parameter can only be set at server start. See also . @@ -578,7 +575,7 @@ include_dir 'conf.d' - external_pid_file (string) + external_pid_file (string) - has no default value external_pid_file configuration parameter @@ -642,7 +639,7 @@ include_dir 'conf.d' - listen_addresses (string) + listen_addresses (string) - default is localhost listen_addresses configuration parameter @@ -661,9 +658,8 @@ include_dir 'conf.d' to it. If the list is not empty, the server will start if it can listen on at least one TCP/IP address. A warning will be emitted for any TCP/IP address which cannot be opened. - The default value is localhost, - which allows only local TCP/IP loopback connections to be - made. + Localhost value allows only local TCP/IP loopback + connections to be made. While client authentication ( - port (integer) + port (integer) - default is 5432 port configuration parameter - The TCP port the server listens on; 5432 by default. Note that the + The TCP port the server listens on. Note that the same port number is used for all IP addresses the server listens on. This parameter can only be set at server start. @@ -693,7 +689,7 @@ include_dir 'conf.d' - max_connections (integer) + max_connections (integer) - default is 100 max_connections configuration parameter @@ -701,8 +697,7 @@ include_dir 'conf.d' Determines the maximum number of concurrent connections to the - database server. The default is typically 100 connections, but - might be less if your kernel settings will not support it (as + database server. This value can be less than 100 if your kernel settings does not support it (as determined during initdb). This parameter can only be set at server start. @@ -722,7 +717,7 @@ include_dir 'conf.d' - reserved_connections (integer) + reserved_connections (integer) - default is 0 reserved_connections configuration parameter @@ -744,8 +739,7 @@ include_dir 'conf.d' - The default value is zero connections. The value must be less than - max_connections minus + The value must be less than max_connections minus superuser_reserved_connections. This parameter can only be set at server start. @@ -755,7 +749,7 @@ include_dir 'conf.d' superuser_reserved_connections - (integer) + (integer) - default is 3 superuser_reserved_connections configuration parameter @@ -776,8 +770,7 @@ include_dir 'conf.d' - The default value is three connections. The value must be less - than max_connections minus + The value must be less than max_connections minus reserved_connections. This parameter can only be set at server start. @@ -785,7 +778,7 @@ include_dir 'conf.d' - unix_socket_directories (string) + unix_socket_directories (string) - default is /tmp, on Windows '' unix_socket_directories configuration parameter @@ -816,10 +809,8 @@ include_dir 'conf.d' - The default value is normally - /tmp, but that can be changed at build time. - On Windows, the default is empty, which means no Unix-domain socket is - created by default. + The value can be changed at build time. + On Windows, which means no Unix-domain socket is created by default. This parameter can only be set at server start. @@ -836,7 +827,7 @@ include_dir 'conf.d' - unix_socket_group (string) + unix_socket_group (string) - default is '' unix_socket_group configuration parameter @@ -848,7 +839,7 @@ include_dir 'conf.d' server.) In combination with the parameter unix_socket_permissions this can be used as an additional access control mechanism for Unix-domain connections. - By default this is the empty string, which uses the default + If an empty string is used then it uses the default group of the server user. This parameter can only be set at server start. @@ -862,7 +853,7 @@ include_dir 'conf.d' - unix_socket_permissions (integer) + unix_socket_permissions (integer) - default is 0777 unix_socket_permissions configuration parameter @@ -879,7 +870,7 @@ include_dir 'conf.d' - The default permissions are 0777, meaning + If 0777 is used, then anyone can connect. Reasonable alternatives are 0770 (only user and group, see also unix_socket_group) and 0700 @@ -912,7 +903,7 @@ include_dir 'conf.d' - bonjour (boolean) + bonjour (boolean) - default is off bonjour configuration parameter @@ -920,14 +911,14 @@ include_dir 'conf.d' Enables advertising the server's existence via - Bonjour. The default is off. + Bonjour. This parameter can only be set at server start. - bonjour_name (string) + bonjour_name (string) - default is '' bonjour_name configuration parameter @@ -935,8 +926,8 @@ include_dir 'conf.d' Specifies the Bonjour service - name. The computer name is used if this parameter is set to the - empty string '' (which is the default). This parameter is + name. The computer name is used if this parameter is set to an + empty string. This parameter is ignored if the server was not compiled with Bonjour support. This parameter can only be set at server start. @@ -952,7 +943,7 @@ include_dir 'conf.d' - tcp_keepalives_idle (integer) + tcp_keepalives_idle (integer) - default is 0 tcp_keepalives_idle configuration parameter @@ -962,7 +953,7 @@ include_dir 'conf.d' Specifies the amount of time with no network activity after which the operating system should send a TCP keepalive message to the client. If this value is specified without units, it is taken as seconds. - A value of 0 (the default) selects the operating system's default. + A value of 0 selects the operating system's default. On Windows, setting a value of 0 will set this parameter to 2 hours, since Windows does not provide a way to read the system default value. This parameter is supported only on systems that support @@ -975,7 +966,7 @@ include_dir 'conf.d' - tcp_keepalives_interval (integer) + tcp_keepalives_interval (integer) - default is 0 tcp_keepalives_interval configuration parameter @@ -985,7 +976,7 @@ include_dir 'conf.d' Specifies the amount of time after which a TCP keepalive message that has not been acknowledged by the client should be retransmitted. If this value is specified without units, it is taken as seconds. - A value of 0 (the default) selects the operating system's default. + A value of 0 selects the operating system's default. On Windows, setting a value of 0 will set this parameter to 1 second, since Windows does not provide a way to read the system default value. This parameter is supported only on systems that support @@ -998,7 +989,7 @@ include_dir 'conf.d' - tcp_keepalives_count (integer) + tcp_keepalives_count (integer) - default is 0 tcp_keepalives_count configuration parameter @@ -1007,7 +998,7 @@ include_dir 'conf.d' Specifies the number of TCP keepalive messages that can be lost before the server's connection to the client is considered dead. - A value of 0 (the default) selects the operating system's default. + A value of 0 selects the operating system's default. This parameter is supported only on systems that support TCP_KEEPCNT or an equivalent socket option (which does not include Windows); on other systems, it must be zero. @@ -1018,7 +1009,7 @@ include_dir 'conf.d' - tcp_user_timeout (integer) + tcp_user_timeout (integer) - default is 0 tcp_user_timeout configuration parameter @@ -1028,7 +1019,7 @@ include_dir 'conf.d' Specifies the amount of time that transmitted data may remain unacknowledged before the TCP connection is forcibly closed. If this value is specified without units, it is taken as milliseconds. - A value of 0 (the default) selects the operating system's default. + A value of 0 selects the operating system's default. This parameter is supported only on systems that support TCP_USER_TIMEOUT (which does not include Windows); on other systems, it must be zero. In sessions connected via a Unix-domain socket, this parameter is @@ -1038,7 +1029,7 @@ include_dir 'conf.d' - client_connection_check_interval (integer) + client_connection_check_interval (integer) - default is 0 client_connection_check_interval configuration parameter @@ -1057,7 +1048,7 @@ include_dir 'conf.d' If the value is specified without units, it is taken as milliseconds. - The default value is 0, which disables connection + If 0 is used, then disables connection checks. Without connection checks, the server will detect the loss of the connection only at the next interaction with the socket, when it waits for, receives or sends data. @@ -1082,7 +1073,7 @@ include_dir 'conf.d' - authentication_timeout (integer) + authentication_timeout (integer) - default is 1 minute timeoutclient authentication client authenticationtimeout during @@ -1097,7 +1088,6 @@ include_dir 'conf.d' this much time, the server closes the connection. This prevents hung clients from occupying a connection indefinitely. If this value is specified without units, it is taken as seconds. - The default is one minute (1m). This parameter can only be set in the postgresql.conf file or on the server command line. @@ -1105,7 +1095,7 @@ include_dir 'conf.d' - password_encryption (enum) + password_encryption (enum) - default is scram-sha-256 password_encryption configuration parameter @@ -1117,7 +1107,7 @@ include_dir 'conf.d' algorithm to use to encrypt the password. Possible values are scram-sha-256, which will encrypt the password with SCRAM-SHA-256, and md5, which stores the password - as an MD5 hash. The default is scram-sha-256. + as an MD5 hash. Note that older clients might lack support for the SCRAM authentication @@ -1136,7 +1126,7 @@ include_dir 'conf.d' - scram_iterations (integer) + scram_iterations (integer) - default is 4096 scram_iterations configuration parameter @@ -1144,7 +1134,7 @@ include_dir 'conf.d' The number of computational iterations to be performed when encrypting - a password using SCRAM-SHA-256. The default is 4096. + a password using SCRAM-SHA-256. A higher number of iterations provides additional protection against brute-force attacks on stored passwords, but makes authentication slower. Changing the value has no effect on existing passwords @@ -1156,15 +1146,14 @@ include_dir 'conf.d' - krb_server_keyfile (string) + krb_server_keyfile (string) - default is FILE:/usr/local/pgsql/etc/krb5.keytab krb_server_keyfile configuration parameter - Sets the location of the server's Kerberos key file. The default is - FILE:/usr/local/pgsql/etc/krb5.keytab + Sets the location of the server's Kerberos key file. (where the directory part is whatever was specified as sysconfdir at build time; use pg_config --sysconfdir to determine that). @@ -1178,7 +1167,7 @@ include_dir 'conf.d' - krb_caseins_users (boolean) + krb_caseins_users (boolean) - default is off (case sensitive) krb_caseins_users configuration parameter @@ -1187,14 +1176,14 @@ include_dir 'conf.d' Sets whether GSSAPI user names should be treated case-insensitively. - The default is off (case sensitive). This parameter can only be - set in the postgresql.conf file or on the server command line. + This parameter can only be set in the postgresql.conf + file or on the server command line. - gss_accept_delegation (boolean) + gss_accept_delegation (boolean) - default is off gss_accept_delegation configuration parameter @@ -1202,7 +1191,7 @@ include_dir 'conf.d' Sets whether GSSAPI delegation should be accepted from the client. - The default is off meaning credentials from the client will + Value off means credentials from the client will not be accepted. Changing this to on will make the server accept credentials delegated to it from the client. This parameter can only be set in the postgresql.conf file or on the server command line. @@ -1253,7 +1242,7 @@ include_dir 'conf.d' - ssl (boolean) + ssl (boolean) - default is off ssl configuration parameter @@ -1263,13 +1252,12 @@ include_dir 'conf.d' Enables SSL connections. This parameter can only be set in the postgresql.conf file or on the server command line. - The default is off. - ssl_ca_file (string) + ssl_ca_file (string) - default is '' ssl_ca_file configuration parameter @@ -1281,14 +1269,14 @@ include_dir 'conf.d' Relative paths are relative to the data directory. This parameter can only be set in the postgresql.conf file or on the server command line. - The default is empty, meaning no CA file is loaded, + An empty string for this value means no CA file is loaded, and client certificate verification is not performed. - ssl_cert_file (string) + ssl_cert_file (string) - default is server.crt ssl_cert_file configuration parameter @@ -1299,13 +1287,12 @@ include_dir 'conf.d' Relative paths are relative to the data directory. This parameter can only be set in the postgresql.conf file or on the server command line. - The default is server.crt. - ssl_crl_file (string) + ssl_crl_file (string) - default is '' ssl_crl_file configuration parameter @@ -1317,14 +1304,14 @@ include_dir 'conf.d' Relative paths are relative to the data directory. This parameter can only be set in the postgresql.conf file or on the server command line. - The default is empty, meaning no CRL file is loaded (unless + Value of an empty string means no CRL file is loaded (unless is set). - ssl_crl_dir (string) + ssl_crl_dir (string) - default is '' ssl_crl_dir configuration parameter @@ -1335,7 +1322,7 @@ include_dir 'conf.d' certificate revocation list (CRL). Relative paths are relative to the data directory. This parameter can only be set in the postgresql.conf file or on the server command - line. The default is empty, meaning no CRLs are used (unless + line. Value of an empty string means no CRLs are used (unless is set). @@ -1358,7 +1345,7 @@ include_dir 'conf.d' - ssl_key_file (string) + ssl_key_file (string) - default is server.key ssl_key_file configuration parameter @@ -1369,7 +1356,6 @@ include_dir 'conf.d' Relative paths are relative to the data directory. This parameter can only be set in the postgresql.conf file or on the server command line. - The default is server.key. @@ -1397,7 +1383,7 @@ include_dir 'conf.d' - ssl_ciphers (string) + ssl_ciphers (string) - default is HIGH:MEDIUM:+3DES:!aNULL ssl_ciphers configuration parameter @@ -1409,8 +1395,7 @@ include_dir 'conf.d' for TLS version 1.3 connections. See the ciphers manual page in the OpenSSL package for the - syntax of this setting and a list of supported values. The default value - is HIGH:MEDIUM:+3DES:!aNULL. The default is usually a + syntax of this setting and a list of supported values. The default is usually a reasonable choice unless you have specific security requirements. @@ -1482,7 +1467,7 @@ include_dir 'conf.d' - ssl_prefer_server_ciphers (boolean) + ssl_prefer_server_ciphers (boolean) - default is on ssl_prefer_server_ciphers configuration parameter @@ -1493,7 +1478,6 @@ include_dir 'conf.d' than the client's. This parameter can only be set in the postgresql.conf file or on the server command line. - The default is on. @@ -1507,7 +1491,7 @@ include_dir 'conf.d' - ssl_groups (string) + ssl_groups (string) - default is X25519:prime256v1 ssl_groups configuration parameter @@ -1520,7 +1504,6 @@ include_dir 'conf.d' It does not need to be the same curve used by the server's Elliptic Curve key. This parameter can only be set in the postgresql.conf file or on the server command line. - The default is X25519:prime256v1. @@ -1544,7 +1527,7 @@ include_dir 'conf.d' - ssl_min_protocol_version (enum) + ssl_min_protocol_version (enum) - default is TLSv1.2 ssl_min_protocol_version configuration parameter @@ -1561,7 +1544,7 @@ include_dir 'conf.d' - The default is TLSv1.2, which satisfies industry + Value of TLSv1.2 usually satisfies industry best practices as of this writing. @@ -1573,7 +1556,7 @@ include_dir 'conf.d' - ssl_max_protocol_version (enum) + ssl_max_protocol_version (enum) - default is to allow any version ssl_max_protocol_version configuration parameter @@ -1582,8 +1565,7 @@ include_dir 'conf.d' Sets the maximum SSL/TLS protocol version to use. Valid values are as for , with addition of - an empty string, which allows any protocol version. The default is to - allow any version. Setting the maximum protocol version is mainly + an empty string, which allows any protocol version. Setting the maximum protocol version is mainly useful for testing or if some component has issues working with a newer protocol. @@ -1596,7 +1578,7 @@ include_dir 'conf.d' - ssl_dh_params_file (string) + ssl_dh_params_file (string) - default is '' ssl_dh_params_file configuration parameter @@ -1604,8 +1586,8 @@ include_dir 'conf.d' Specifies the name of the file containing Diffie-Hellman parameters - used for so-called ephemeral DH family of SSL ciphers. The default is - empty, in which case compiled-in default DH parameters used. Using + used for so-called ephemeral DH family of SSL ciphers. Using an empty string a compiled-in + default DH parameters is used. Using custom DH parameters reduces the exposure if an attacker manages to crack the well-known compiled-in DH parameters. You can create your own DH parameters file with the command @@ -1620,7 +1602,7 @@ include_dir 'conf.d' - ssl_passphrase_command (string) + ssl_passphrase_command (string) - default is '' ssl_passphrase_command configuration parameter @@ -1628,9 +1610,8 @@ include_dir 'conf.d' Sets an external command to be invoked when a passphrase for - decrypting an SSL file such as a private key needs to be obtained. By - default, this parameter is empty, which means the built-in prompting - mechanism is used. + decrypting an SSL file such as a private key needs to be obtained. + An empty string means the built-in prompting mechanism is used. The command must print the passphrase to the standard output and exit @@ -1654,7 +1635,7 @@ include_dir 'conf.d' - ssl_passphrase_command_supports_reload (boolean) + ssl_passphrase_command_supports_reload (boolean) - default is off ssl_passphrase_command_supports_reload configuration parameter @@ -1664,8 +1645,7 @@ include_dir 'conf.d' This parameter determines whether the passphrase command set by ssl_passphrase_command will also be called during a configuration reload if a key file needs a passphrase. If this - parameter is off (the default), then - ssl_passphrase_command will be ignored during a + parameter is off, then ssl_passphrase_command will be ignored during a reload and the SSL configuration will not be reloaded if a passphrase is needed. That setting is appropriate for a command that requires a TTY for prompting, which might not be available when the server is @@ -1690,7 +1670,7 @@ include_dir 'conf.d' - shared_buffers (integer) + shared_buffers (integer) - default is 128MB shared_buffers configuration parameter @@ -1698,8 +1678,8 @@ include_dir 'conf.d' Sets the amount of memory the database server uses for shared - memory buffers. The default is typically 128 megabytes - (128MB), but might be less if your kernel settings will + memory buffers. This value is typically (128MB), + but might be less if your kernel settings does not support it (as determined during initdb). This setting must be at least 128 kilobytes. However, settings significantly higher than the minimum are usually needed @@ -1735,7 +1715,7 @@ include_dir 'conf.d' - huge_pages (enum) + huge_pages (enum) - default is try huge_pages configuration parameter @@ -1743,7 +1723,7 @@ include_dir 'conf.d' Controls whether huge pages are requested for the main shared memory - area. Valid values are try (the default), + area. Valid values are try, on, and off. With huge_pages set to try, the server will try to request huge pages, but fall back to the default if @@ -1758,8 +1738,7 @@ include_dir 'conf.d' At present, this setting is supported only on Linux and Windows. The setting is ignored on other systems when set to try. On Linux, it is only supported when - shared_memory_type is set to mmap - (the default). + shared_memory_type is set to mmap, its default value. @@ -1798,7 +1777,7 @@ include_dir 'conf.d' - huge_page_size (integer) + huge_page_size (integer) - default is 0 huge_page_size configuration parameter @@ -1807,7 +1786,6 @@ include_dir 'conf.d' Controls the size of huge pages, when they are enabled with . - The default is zero (0). When set to 0, the default huge page size on the system will be used. This parameter can only be set at server start. @@ -1825,7 +1803,7 @@ include_dir 'conf.d' - temp_buffers (integer) + temp_buffers (integer) - default is 8MB temp_buffers configuration parameter @@ -1837,7 +1815,6 @@ include_dir 'conf.d' for access to temporary tables. If this value is specified without units, it is taken as blocks, that is BLCKSZ bytes, typically 8kB. - The default is eight megabytes (8MB). (If BLCKSZ is not 8kB, the default value scales proportionally to it.) This setting can be changed within individual @@ -1859,7 +1836,7 @@ include_dir 'conf.d' - max_prepared_transactions (integer) + max_prepared_transactions (integer) - default is 0 max_prepared_transactions configuration parameter @@ -1869,8 +1846,7 @@ include_dir 'conf.d' Sets the maximum number of transactions that can be in the prepared state simultaneously (see ). - Setting this parameter to zero (which is the default) - disables the prepared-transaction feature. + With value of 0 then disables the prepared-transaction feature. This parameter can only be set at server start. @@ -1892,7 +1868,7 @@ include_dir 'conf.d' - work_mem (integer) + work_mem (integer) - default is 4MB work_mem configuration parameter @@ -1902,7 +1878,6 @@ include_dir 'conf.d' Sets the base maximum amount of memory to be used by a query operation (such as a sort or hash table) before writing to temporary disk files. If this value is specified without units, it is taken as kilobytes. - The default value is four megabytes (4MB). Note that a complex query might perform several sort and hash operations at the same time, with each operation generally being allowed to use as much memory as this value specifies before @@ -1931,7 +1906,7 @@ include_dir 'conf.d' - hash_mem_multiplier (floating point) + hash_mem_multiplier (floating point) - default is 2.0 hash_mem_multiplier configuration parameter @@ -1941,8 +1916,8 @@ include_dir 'conf.d' Used to compute the maximum amount of memory that hash-based operations can use. The final limit is determined by multiplying work_mem by - hash_mem_multiplier. The default value is - 2.0, which makes hash-based operations use twice the usual + hash_mem_multiplier. + Value of 2.0 makes hash-based operations use twice the usual work_mem base amount. @@ -1951,7 +1926,7 @@ include_dir 'conf.d' occurrence, especially when simply increasing work_mem results in memory pressure (memory pressure typically takes the form of intermittent out of - memory errors). The default setting of 2.0 is often effective with + memory errors). The value of 2.0 is often effective with mixed workloads. Higher settings in the range of 2.0 - 8.0 or more may be effective in environments where work_mem has already been increased to 40MB @@ -1961,7 +1936,7 @@ include_dir 'conf.d' - maintenance_work_mem (integer) + maintenance_work_mem (integer) - default is 64MB maintenance_work_mem configuration parameter @@ -1972,9 +1947,7 @@ include_dir 'conf.d' operations, such as VACUUM, CREATE INDEX, and ALTER TABLE ADD FOREIGN KEY. If this value is specified without units, it is taken as kilobytes. - It defaults - to 64 megabytes (64MB). Since only one of these - operations can be executed at a time by a database session, and + Since only one of these operations can be executed at a time by a database session, and an installation normally doesn't have many of them running concurrently, it's safe to set this value significantly larger than work_mem. Larger settings might improve @@ -1991,7 +1964,7 @@ include_dir 'conf.d' - autovacuum_work_mem (integer) + autovacuum_work_mem (integer) - default is -1 autovacuum_work_mem configuration parameter @@ -2001,8 +1974,7 @@ include_dir 'conf.d' Specifies the maximum amount of memory to be used by each autovacuum worker process. If this value is specified without units, it is taken as kilobytes. - It defaults to -1, indicating that - the value of should + Value of -1 indicates should be used instead. The setting has no effect on the behavior of VACUUM when run in other contexts. This parameter can only be set in the @@ -2014,7 +1986,7 @@ include_dir 'conf.d' - vacuum_buffer_usage_limit (integer) + vacuum_buffer_usage_limit (integer) - default is 2MB vacuum_buffer_usage_limit configuration parameter @@ -2029,8 +2001,7 @@ include_dir 'conf.d' valid sizes range from 128 kB to 16 GB. If the specified size would exceed 1/8 the size of shared_buffers, the size is silently capped - to that value. The default value is 2MB. If - this value is specified without units, it is taken as kilobytes. This + to that value. If this value is specified without units, it is taken as kilobytes. This parameter can be set at any time. It can be overridden for and when passing the option. Higher @@ -2043,7 +2014,7 @@ include_dir 'conf.d' - logical_decoding_work_mem (integer) + logical_decoding_work_mem (integer) - default is 64MB logical_decoding_work_mem configuration parameter @@ -2052,8 +2023,7 @@ include_dir 'conf.d' Specifies the maximum amount of memory to be used by logical decoding, before some of the decoded changes are written to local disk. This - limits the amount of memory used by logical streaming replication - connections. It defaults to 64 megabytes (64MB). + limits the amount of memory used by logical streaming replication connections. Since each replication connection only uses a single buffer of this size, and an installation normally doesn't have many such connections concurrently (as limited by max_wal_senders), it's @@ -2064,7 +2034,7 @@ include_dir 'conf.d' - commit_timestamp_buffers (integer) + commit_timestamp_buffers (integer) - default is 0 commit_timestamp_buffers configuration parameter @@ -2076,7 +2046,7 @@ include_dir 'conf.d' ). If this value is specified without units, it is taken as blocks, that is BLCKSZ bytes, typically 8kB. - The default value is 0, which requests + With value of 0 requests shared_buffers/512 up to 1024 blocks, but not fewer than 16 blocks. This parameter can only be set at server start. @@ -2085,7 +2055,7 @@ include_dir 'conf.d' - multixact_member_buffers (integer) + multixact_member_buffers (integer) - default is 32 multixact_member_buffers configuration parameter @@ -2097,14 +2067,13 @@ include_dir 'conf.d' ). If this value is specified without units, it is taken as blocks, that is BLCKSZ bytes, typically 8kB. - The default value is 32. This parameter can only be set at server start. - multixact_offset_buffers (integer) + multixact_offset_buffers (integer) - default is 16 multixact_offset_buffers configuration parameter @@ -2116,14 +2085,13 @@ include_dir 'conf.d' ). If this value is specified without units, it is taken as blocks, that is BLCKSZ bytes, typically 8kB. - The default value is 16. This parameter can only be set at server start. - notify_buffers (integer) + notify_buffers (integer) - default is 16 notify_buffers configuration parameter @@ -2135,14 +2103,13 @@ include_dir 'conf.d' ). If this value is specified without units, it is taken as blocks, that is BLCKSZ bytes, typically 8kB. - The default value is 16. This parameter can only be set at server start. - serializable_buffers (integer) + serializable_buffers (integer) - default is 32 serializable_buffers configuration parameter @@ -2154,14 +2121,13 @@ include_dir 'conf.d' ). If this value is specified without units, it is taken as blocks, that is BLCKSZ bytes, typically 8kB. - The default value is 32. This parameter can only be set at server start. - subtransaction_buffers (integer) + subtransaction_buffers (integer) - default is 0 subtransaction_buffers configuration parameter @@ -2173,7 +2139,7 @@ include_dir 'conf.d' ). If this value is specified without units, it is taken as blocks, that is BLCKSZ bytes, typically 8kB. - The default value is 0, which requests + Value of 0 requests shared_buffers/512 up to 1024 blocks, but not fewer than 16 blocks. This parameter can only be set at server start. @@ -2182,7 +2148,7 @@ include_dir 'conf.d' - transaction_buffers (integer) + transaction_buffers (integer) - default is 0 transaction_buffers configuration parameter @@ -2194,7 +2160,7 @@ include_dir 'conf.d' ). If this value is specified without units, it is taken as blocks, that is BLCKSZ bytes, typically 8kB. - The default value is 0, which requests + Value of 0 requests shared_buffers/512 up to 1024 blocks, but not fewer than 16 blocks. This parameter can only be set at server start. @@ -2203,7 +2169,7 @@ include_dir 'conf.d' - max_stack_depth (integer) + max_stack_depth (integer) - default is 2MB max_stack_depth configuration parameter @@ -2217,7 +2183,7 @@ include_dir 'conf.d' margin is needed because the stack depth is not checked in every routine in the server, but only in key potentially-recursive routines. If this value is specified without units, it is taken as kilobytes. - The default setting is two megabytes (2MB), which + Setting this value to (2MB), which is conservatively small and unlikely to risk crashes. However, it might be too small to allow execution of complex functions. Only superusers and users with the appropriate SET @@ -2237,7 +2203,7 @@ include_dir 'conf.d' - shared_memory_type (enum) + shared_memory_type (enum) - default is first supported option for that platform shared_memory_type configuration parameter @@ -2251,8 +2217,7 @@ include_dir 'conf.d' anonymous shared memory allocated using mmap), sysv (for System V shared memory allocated via shmget) and windows (for Windows - shared memory). Not all values are supported on all platforms; the - first supported option is the default for that platform. The use of + shared memory). Not all values are supported on all platforms. The use of the sysv option, which is not the default on any platform, is generally discouraged because it typically requires non-default kernel settings to allow for large allocations (see - dynamic_shared_memory_type (enum) + dynamic_shared_memory_type (enum) - default is first supported option for that platform dynamic_shared_memory_type configuration parameter @@ -2276,8 +2241,7 @@ include_dir 'conf.d' windows (for Windows shared memory), and mmap (to simulate shared memory using memory-mapped files stored in the data directory). - Not all values are supported on all platforms; the first supported - option is usually the default for that platform. The use of the + Not all values are supported on all platforms. The use of the mmap option, which is not the default on any platform, is generally discouraged because the operating system may write modified pages back to disk repeatedly, increasing system I/O load; @@ -2289,7 +2253,7 @@ include_dir 'conf.d' - min_dynamic_shared_memory (integer) + min_dynamic_shared_memory (integer) - default is 0 min_dynamic_shared_memory configuration parameter @@ -2307,8 +2271,7 @@ include_dir 'conf.d' the huge_pages setting on operating systems where that is supported, and may be more likely to benefit from larger pages on operating systems where that is managed automatically. - The default value is 0 (none). This parameter can - only be set at server start. + This parameter can only be set at server start. @@ -2321,7 +2284,7 @@ include_dir 'conf.d' - temp_file_limit (integer) + temp_file_limit (integer) - default is -1 temp_file_limit configuration parameter @@ -2333,7 +2296,7 @@ include_dir 'conf.d' storage file for a held cursor. A transaction attempting to exceed this limit will be canceled. If this value is specified without units, it is taken as kilobytes. - -1 (the default) means no limit. + Value of -1 means no limit. Only superusers and users with the appropriate SET privilege can change this setting. @@ -2386,7 +2349,7 @@ include_dir 'conf.d' - max_notify_queue_pages (integer) + max_notify_queue_pages (integer) - default is 1048576 max_notify_queue_pages configuration parameter @@ -2395,8 +2358,7 @@ include_dir 'conf.d' Specifies the maximum amount of allocated pages for / queue. - The default value is 1048576. For 8 KB pages it allows to consume - up to 8 GB of disk space. + For 8 KB pages it allows to consume up to 8 GB of disk space. @@ -2409,7 +2371,7 @@ include_dir 'conf.d' - max_files_per_process (integer) + max_files_per_process (integer) - default is 1000 files max_files_per_process configuration parameter @@ -2418,8 +2380,7 @@ include_dir 'conf.d' Sets the maximum number of open files each server subprocess is allowed to open simultaneously; files already opened in the - postmaster are not counted toward this limit. The default is one - thousand files. + postmaster are not counted toward this limit. If the kernel is enforcing @@ -2459,7 +2420,7 @@ include_dir 'conf.d' - bgwriter_delay (integer) + bgwriter_delay (integer) - default is 200ms bgwriter_delay configuration parameter @@ -2475,8 +2436,7 @@ include_dir 'conf.d' buffer pool, though, it goes into a longer sleep regardless of bgwriter_delay. If this value is specified without units, it is taken as milliseconds. - The default value is 200 - milliseconds (200ms). Note that on some systems, the + Note that on some systems, the effective resolution of sleep delays is 10 milliseconds; setting bgwriter_delay to a value that is not a multiple of 10 might have the same results as setting it to the next higher multiple @@ -2487,7 +2447,7 @@ include_dir 'conf.d' - bgwriter_lru_maxpages (integer) + bgwriter_lru_maxpages (integer) - default is 100 buffers bgwriter_lru_maxpages configuration parameter @@ -2498,7 +2458,6 @@ include_dir 'conf.d' by the background writer. Setting this to zero disables background writing. (Note that checkpoints, which are managed by a separate, dedicated auxiliary process, are unaffected.) - The default value is 100 buffers. This parameter can only be set in the postgresql.conf file or on the server command line. @@ -2506,7 +2465,7 @@ include_dir 'conf.d' - bgwriter_lru_multiplier (floating point) + bgwriter_lru_multiplier (floating point) - default is 2.0 bgwriter_lru_multiplier configuration parameter @@ -2526,7 +2485,6 @@ include_dir 'conf.d' Larger values provide some cushion against spikes in demand, while smaller values intentionally leave writes to be done by server processes. - The default is 2.0. This parameter can only be set in the postgresql.conf file or on the server command line. @@ -2534,7 +2492,7 @@ include_dir 'conf.d' - bgwriter_flush_after (integer) + bgwriter_flush_after (integer) - default is 512kB on Linux, 0 elsewhere bgwriter_flush_after configuration parameter @@ -2556,8 +2514,7 @@ include_dir 'conf.d' that is BLCKSZ bytes, typically 8kB. The valid range is between 0, which disables forced writeback, and - 2MB. The default is 512kB on Linux, - 0 elsewhere. (If BLCKSZ is not 8kB, + 2MB. (If BLCKSZ is not 8kB, the default and maximum values scale proportionally to it.) This parameter can only be set in the postgresql.conf file or on the server command line. @@ -2580,7 +2537,7 @@ include_dir 'conf.d' - backend_flush_after (integer) + backend_flush_after (integer) - default is 0 backend_flush_after configuration parameter @@ -2602,7 +2559,7 @@ include_dir 'conf.d' that is BLCKSZ bytes, typically 8kB. The valid range is between 0, which disables forced writeback, - and 2MB. The default is 0, i.e., no + and 2MB. If 0 is used then no forced writeback. (If BLCKSZ is not 8kB, the maximum value scales proportionally to it.) @@ -2649,7 +2606,7 @@ include_dir 'conf.d' - maintenance_io_concurrency (integer) + maintenance_io_concurrency (integer) - default is 16 on supported systems, otherwise 0 maintenance_io_concurrency configuration parameter @@ -2689,7 +2646,7 @@ include_dir 'conf.d' - io_combine_limit (integer) + io_combine_limit (integer) - default is 128kb io_combine_limit configuration parameter @@ -2797,7 +2754,7 @@ include_dir 'conf.d' - max_worker_processes (integer) + max_worker_processes (integer) - default is 8 max_worker_processes configuration parameter @@ -2805,8 +2762,7 @@ include_dir 'conf.d' Sets the maximum number of background processes that the cluster - can support. This parameter can only be set at server start. The - default is 8. + can support. This parameter can only be set at server start. @@ -2825,7 +2781,7 @@ include_dir 'conf.d' - max_parallel_workers_per_gather (integer) + max_parallel_workers_per_gather (integer) - default is 2 max_parallel_workers_per_gather configuration parameter @@ -2839,8 +2795,7 @@ include_dir 'conf.d' . Note that the requested number of workers may not actually be available at run time. If this occurs, the plan will run with fewer workers than expected, which may - be inefficient. The default value is 2. Setting this value to 0 - disables parallel query execution. + be inefficient. Setting this value to 0 disables parallel query execution. @@ -2867,7 +2822,7 @@ include_dir 'conf.d' - max_parallel_maintenance_workers (integer) + max_parallel_maintenance_workers (integer) - default is 2 max_parallel_maintenance_workers configuration parameter @@ -2884,7 +2839,7 @@ include_dir 'conf.d' by . Note that the requested number of workers may not actually be available at run time. If this occurs, the utility operation will run with fewer - workers than expected. The default value is 2. Setting this + workers than expected. Setting this value to 0 disables the use of parallel workers by utility commands. @@ -2905,7 +2860,7 @@ include_dir 'conf.d' - max_parallel_workers (integer) + max_parallel_workers (integer) - default is 8 max_parallel_workers configuration parameter @@ -2913,7 +2868,7 @@ include_dir 'conf.d' Sets the maximum number of workers that the cluster can support for - parallel operations. The default value is 8. When increasing or + parallel operations. When increasing or decreasing this value, consider also adjusting and . @@ -2927,7 +2882,7 @@ include_dir 'conf.d' - parallel_leader_participation (boolean) + parallel_leader_participation (boolean) - default is on parallel_leader_participation configuration parameter @@ -2936,8 +2891,7 @@ include_dir 'conf.d' Allows the leader process to execute the query plan under Gather and Gather Merge nodes - instead of waiting for worker processes. The default is - on. Setting this value to off + instead of waiting for worker processes. Setting this value to off reduces the likelihood that workers will become blocked because the leader is not reading tuples fast enough, but requires the leader process to wait for worker processes to start up before the first @@ -2964,7 +2918,7 @@ include_dir 'conf.d' - wal_level (enum) + wal_level (enum) - default is replica wal_level configuration parameter @@ -2972,7 +2926,7 @@ include_dir 'conf.d' wal_level determines how much information is written to - the WAL. The default value is replica, which writes enough + the WAL. When value is replica then it is written enough data to support WAL archiving and replication, including running read-only queries on a standby server. minimal removes all logging except the information required to recover from a crash or @@ -3025,7 +2979,7 @@ include_dir 'conf.d' - fsync (boolean) + fsync (boolean) - has no default value fsync configuration parameter @@ -3087,7 +3041,7 @@ include_dir 'conf.d' - synchronous_commit (enum) + synchronous_commit (enum) - default is on synchronous_commit configuration parameter @@ -3097,8 +3051,7 @@ include_dir 'conf.d' Specifies how much WAL processing must complete before the database server returns a success indication to the client. Valid values are - remote_apply, on - (the default), remote_write, + remote_apply, on, remote_write, local, and off. @@ -3242,7 +3195,7 @@ include_dir 'conf.d' - wal_sync_method (enum) + wal_sync_method (enum) - default is the first method supported by the platform wal_sync_method configuration parameter @@ -3297,7 +3250,7 @@ include_dir 'conf.d' - full_page_writes (boolean) + full_page_writes (boolean) - default is on full_page_writes configuration parameter @@ -3338,13 +3291,12 @@ include_dir 'conf.d' This parameter can only be set in the postgresql.conf file or on the server command line. - The default is on. - wal_log_hints (boolean) + wal_log_hints (boolean) - default is off wal_log_hints configuration parameter @@ -3365,13 +3317,13 @@ include_dir 'conf.d' - This parameter can only be set at server start. The default value is off. + This parameter can only be set at server start. - wal_compression (enum) + wal_compression (enum) - default is off wal_compression configuration parameter @@ -3389,7 +3341,6 @@ include_dir 'conf.d' was compiled with ) and zstd (if PostgreSQL was compiled with ). - The default value is off. Only superusers and users with the appropriate SET privilege can change this setting. @@ -3404,14 +3355,14 @@ include_dir 'conf.d' - wal_init_zero (boolean) + wal_init_zero (boolean) - default is on wal_init_zero configuration parameter - If set to on (the default), this option causes new + When this value is set to on, causes new WAL files to be filled with zeroes. On some file systems, this ensures that space is allocated before we need to write WAL records. However, Copy-On-Write (COW) file systems may not benefit @@ -3423,14 +3374,14 @@ include_dir 'conf.d' - wal_recycle (boolean) + wal_recycle (boolean) - default is on wal_recycle configuration parameter - If set to on (the default), this option causes WAL + If this value is on, this option causes WAL files to be recycled by renaming them, avoiding the need to create new ones. On COW file systems, it may be faster to create new ones, so the option is given to disable this behavior. @@ -3439,7 +3390,7 @@ include_dir 'conf.d' - wal_buffers (integer) + wal_buffers (integer) - default is -1 wal_buffers configuration parameter @@ -3447,7 +3398,7 @@ include_dir 'conf.d' The amount of shared memory used for WAL data that has not yet been - written to disk. The default setting of -1 selects a size equal to + written to disk. Value of -1 selects a size equal to 1/32nd (about 3%) of , but not less than 64kB nor more than the size of one WAL segment, typically 16MB. This value can be set @@ -3473,7 +3424,7 @@ include_dir 'conf.d' - wal_writer_delay (integer) + wal_writer_delay (integer) - default is 200ms wal_writer_delay configuration parameter @@ -3489,8 +3440,7 @@ include_dir 'conf.d' produced since, then WAL is only written to the operating system, not flushed to disk. If this value is specified without units, it is taken as milliseconds. - The default value is 200 milliseconds (200ms). Note that - on some systems, the effective resolution of sleep delays is 10 + Note that on some systems, the effective resolution of sleep delays is 10 milliseconds; setting wal_writer_delay to a value that is not a multiple of 10 might have the same results as setting it to the next higher multiple of 10. This parameter can only be set in the @@ -3500,7 +3450,7 @@ include_dir 'conf.d' - wal_writer_flush_after (integer) + wal_writer_flush_after (integer) - default is 1MB wal_writer_flush_after configuration parameter @@ -3516,7 +3466,6 @@ include_dir 'conf.d' to 0 then WAL data is always flushed immediately. If this value is specified without units, it is taken as WAL blocks, that is XLOG_BLCKSZ bytes, typically 8kB. - The default is 1MB. This parameter can only be set in the postgresql.conf file or on the server command line. @@ -3524,7 +3473,7 @@ include_dir 'conf.d' - wal_skip_threshold (integer) + wal_skip_threshold (integer) - default is 2MB wal_skip_threshold configuration parameter @@ -3538,14 +3487,13 @@ include_dir 'conf.d' fsync of affected files. Depending on the properties of your storage, raising or lowering this value might help if such commits are slowing concurrent transactions. If this value is specified without units, it - is taken as kilobytes. The default is two megabytes - (2MB). + is taken as kilobytes. - commit_delay (integer) + commit_delay (integer) - default is 0 commit_delay configuration parameter @@ -3565,7 +3513,7 @@ include_dir 'conf.d' when a flush is about to be initiated. Also, no delays are performed if fsync is disabled. If this value is specified without units, it is taken as microseconds. - The default commit_delay is zero (no delay). + Setting this value to 0 means no delay. Only superusers and users with the appropriate SET privilege can change this setting. @@ -3583,7 +3531,7 @@ include_dir 'conf.d' - commit_siblings (integer) + commit_siblings (integer) - default is 5 transactions commit_siblings configuration parameter @@ -3593,8 +3541,7 @@ include_dir 'conf.d' Minimum number of concurrent open transactions to require before performing the commit_delay delay. A larger value makes it more probable that at least one other - transaction will become ready to commit during the delay - interval. The default is five transactions. + transaction will become ready to commit during the delay interval. @@ -3606,7 +3553,7 @@ include_dir 'conf.d' - checkpoint_timeout (integer) + checkpoint_timeout (integer) - default is 5 minutes checkpoint_timeout configuration parameter @@ -3616,7 +3563,6 @@ include_dir 'conf.d' Maximum time between automatic WAL checkpoints. If this value is specified without units, it is taken as seconds. The valid range is between 30 seconds and one day. - The default is five minutes (5min). Increasing this parameter can increase the amount of time needed for crash recovery. This parameter can only be set in the postgresql.conf @@ -3626,7 +3572,7 @@ include_dir 'conf.d' - checkpoint_completion_target (floating point) + checkpoint_completion_target (floating point) - default is 0.9 checkpoint_completion_target configuration parameter @@ -3634,8 +3580,8 @@ include_dir 'conf.d' Specifies the target of checkpoint completion, as a fraction of - total time between checkpoints. The default is 0.9, which spreads the - checkpoint across almost all of the available interval, providing fairly + total time between checkpoints. Value of 0.9 spreads the + checkpoint across to almost all of the available interval, providing fairly consistent I/O load while also leaving some time for checkpoint completion overhead. Reducing this parameter is not recommended because it causes the checkpoint to complete faster. This results in a higher @@ -3648,7 +3594,7 @@ include_dir 'conf.d' - checkpoint_flush_after (integer) + checkpoint_flush_after (integer) - default is 256kb on Linux, elsewhere 0 checkpoint_flush_after configuration parameter @@ -3670,8 +3616,7 @@ include_dir 'conf.d' that is BLCKSZ bytes, typically 8kB. The valid range is between 0, which disables forced writeback, - and 2MB. The default is 256kB on - Linux, 0 elsewhere. (If BLCKSZ is not + and 2MB. (If BLCKSZ is not 8kB, the default and maximum values scale proportionally to it.) This parameter can only be set in the postgresql.conf file or on the server command line. @@ -3680,7 +3625,7 @@ include_dir 'conf.d' - checkpoint_warning (integer) + checkpoint_warning (integer) - default is 30 seconds checkpoint_warning configuration parameter @@ -3692,7 +3637,6 @@ include_dir 'conf.d' than this amount of time (which suggests that max_wal_size ought to be raised). If this value is specified without units, it is taken as seconds. - The default is 30 seconds (30s). Zero disables the warning. No warnings will be generated if checkpoint_timeout is less than checkpoint_warning. @@ -3703,7 +3647,7 @@ include_dir 'conf.d' - max_wal_size (integer) + max_wal_size (integer) - default is 1GB max_wal_size configuration parameter @@ -3716,7 +3660,6 @@ include_dir 'conf.d' heavy load, a failing archive_command or archive_library, or a high wal_keep_size setting. If this value is specified without units, it is taken as megabytes. - The default is 1 GB. Increasing this parameter can increase the amount of time needed for crash recovery. This parameter can only be set in the postgresql.conf @@ -3726,7 +3669,7 @@ include_dir 'conf.d' - min_wal_size (integer) + min_wal_size (integer) - default is 80MB min_wal_size configuration parameter @@ -3739,7 +3682,6 @@ include_dir 'conf.d' handle spikes in WAL usage, for example when running large batch jobs. If this value is specified without units, it is taken as megabytes. - The default is 80 MB. This parameter can only be set in the postgresql.conf file or on the server command line. @@ -3753,7 +3695,7 @@ include_dir 'conf.d' - archive_mode (enum) + archive_mode (enum) - default if off archive_mode configuration parameter @@ -3787,7 +3729,7 @@ include_dir 'conf.d' - archive_command (string) + archive_command (string) - default is '' archive_command configuration parameter @@ -3812,7 +3754,7 @@ include_dir 'conf.d' archive_library is set to an empty string. If both archive_command and archive_library are set, an error will be raised. - If archive_command is an empty string (the default) while + If archive_command is an empty string while archive_mode is enabled (and archive_library is set to an empty string), WAL archiving is temporarily disabled, but the server continues to accumulate WAL segment files in @@ -3827,7 +3769,7 @@ include_dir 'conf.d' - archive_library (string) + archive_library (string) - default is '' archive_library configuration parameter @@ -3835,7 +3777,7 @@ include_dir 'conf.d' The library to use for archiving completed WAL file segments. If set to - an empty string (the default), archiving via shell is enabled, and + an empty string, archiving via shell is enabled, and is used. If both archive_command and archive_library are set, an error will be raised. Otherwise, the specified @@ -3852,7 +3794,7 @@ include_dir 'conf.d' - archive_timeout (integer) + archive_timeout (integer) - default is 0 archive_timeout configuration parameter @@ -3907,7 +3849,7 @@ include_dir 'conf.d' - recovery_prefetch (enum) + recovery_prefetch (enum) - default is try recovery_prefetch configuration parameter @@ -3917,8 +3859,7 @@ include_dir 'conf.d' Whether to try to prefetch blocks that are referenced in the WAL that are not yet in the buffer pool, during recovery. Valid values are off, on and - try (the default). The setting - try enables + try. The setting try enables prefetching only if the operating system provides support for issuing read-ahead advice. @@ -3933,7 +3874,7 @@ include_dir 'conf.d' - wal_decode_buffer_size (integer) + wal_decode_buffer_size (integer) - default is 512kb wal_decode_buffer_size configuration parameter @@ -3943,7 +3884,6 @@ include_dir 'conf.d' A limit on how far ahead the server can look in the WAL, to find blocks to prefetch. If this value is specified without units, it is taken as bytes. - The default is 512kB. @@ -4001,7 +3941,7 @@ include_dir 'conf.d' - restore_command (string) + restore_command (string) - default is '' restore_command configuration parameter @@ -4050,7 +3990,7 @@ restore_command = 'copy "C:\\server\\archivedir\\%f" "%p"' # Windows - archive_cleanup_command (string) + archive_cleanup_command (string) - default is '' archive_cleanup_command configuration parameter @@ -4095,7 +4035,7 @@ restore_command = 'copy "C:\\server\\archivedir\\%f" "%p"' # Windows - recovery_end_command (string) + recovery_end_command (string) - default is '' recovery_end_command configuration parameter @@ -4144,7 +4084,7 @@ restore_command = 'copy "C:\\server\\archivedir\\%f" "%p"' # Windows - recovery_target = 'immediate' + recovery_target (string) - The only possible value is 'immediate' recovery_target configuration parameter @@ -4164,7 +4104,7 @@ restore_command = 'copy "C:\\server\\archivedir\\%f" "%p"' # Windows - recovery_target_name (string) + recovery_target_name (string) - default is '' recovery_target_name configuration parameter @@ -4178,7 +4118,7 @@ restore_command = 'copy "C:\\server\\archivedir\\%f" "%p"' # Windows - recovery_target_time (timestamp) + recovery_target_time (timestamp) - default is '' recovery_target_time configuration parameter @@ -4204,7 +4144,7 @@ restore_command = 'copy "C:\\server\\archivedir\\%f" "%p"' # Windows - recovery_target_xid (string) + recovery_target_xid (string) - default is '' recovery_target_xid configuration parameter @@ -4224,7 +4164,7 @@ restore_command = 'copy "C:\\server\\archivedir\\%f" "%p"' # Windows - recovery_target_lsn (pg_lsn) + recovery_target_lsn (pg_lsn) - default is '' recovery_target_lsn configuration parameter @@ -4249,7 +4189,7 @@ restore_command = 'copy "C:\\server\\archivedir\\%f" "%p"' # Windows - recovery_target_inclusive (boolean) + recovery_target_inclusive (boolean) - default is on recovery_target_inclusive configuration parameter @@ -4264,14 +4204,14 @@ restore_command = 'copy "C:\\server\\archivedir\\%f" "%p"' # Windows is specified. This setting controls whether transactions having exactly the target WAL location (LSN), commit time, or transaction ID, respectively, will - be included in the recovery. Default is on. + be included in the recovery. - recovery_target_timeline (string) + recovery_target_timeline (string) - default is latest recovery_target_timeline configuration parameter @@ -4284,7 +4224,7 @@ restore_command = 'copy "C:\\server\\archivedir\\%f" "%p"' # Windows current when the base backup was taken. The value latest recovers to the latest timeline found in the archive, which is useful in - a standby server. latest is the default. + a standby server. @@ -4306,7 +4246,7 @@ restore_command = 'copy "C:\\server\\archivedir\\%f" "%p"' # Windows - recovery_target_action (enum) + recovery_target_action (enum) - default is pause recovery_target_action configuration parameter @@ -4314,7 +4254,7 @@ restore_command = 'copy "C:\\server\\archivedir\\%f" "%p"' # Windows Specifies what action the server should take once the recovery target is - reached. The default is pause, which means recovery will + reached. Value of pause means recovery will be paused. promote means the recovery process will finish and the server will start to accept connections. Finally shutdown will stop the server after reaching the @@ -4375,7 +4315,7 @@ restore_command = 'copy "C:\\server\\archivedir\\%f" "%p"' # Windows - summarize_wal (boolean) + summarize_wal (boolean) - default is off summarize_wal configuration parameter @@ -4385,7 +4325,7 @@ restore_command = 'copy "C:\\server\\archivedir\\%f" "%p"' # Windows Enables the WAL summarizer process. Note that WAL summarization can be enabled either on a primary or on a standby. This parameter can only be set in the postgresql.conf file or on the server - command line. The default is off. + command line. The server cannot be started with summarize_wal=on @@ -4399,7 +4339,7 @@ restore_command = 'copy "C:\\server\\archivedir\\%f" "%p"' # Windows - wal_summary_keep_time (integer) + wal_summary_keep_time (integer) - default is 10 days wal_summary_keep_time configuration parameter @@ -4419,7 +4359,7 @@ restore_command = 'copy "C:\\server\\archivedir\\%f" "%p"' # Windows This parameter can only be set in the postgresql.conf file or on the server command line. If this value is specified without units, it is taken as minutes. - The default is 10 days. If summarize_wal = off, + If summarize_wal = off, existing WAL summaries will not be removed regardless of the value of this parameter, because the WAL summarizer will not run. @@ -4479,7 +4419,7 @@ restore_command = 'copy "C:\\server\\archivedir\\%f" "%p"' # Windows - max_wal_senders (integer) + max_wal_senders (integer) - default is 10 max_wal_senders configuration parameter @@ -4488,8 +4428,7 @@ restore_command = 'copy "C:\\server\\archivedir\\%f" "%p"' # Windows Specifies the maximum number of concurrent connections from standby servers or streaming base backup clients (i.e., the maximum number of - simultaneously running WAL sender processes). The default is - 10. The value 0 means + simultaneously running WAL sender processes). The value 0 means replication is disabled. Abrupt disconnection of a streaming client might leave an orphaned connection slot behind until a timeout is reached, so this parameter should be set slightly higher than the maximum @@ -4509,7 +4448,7 @@ restore_command = 'copy "C:\\server\\archivedir\\%f" "%p"' # Windows - max_replication_slots (integer) + max_replication_slots (integer) - default is 10 max_replication_slots configuration parameter @@ -4518,8 +4457,7 @@ restore_command = 'copy "C:\\server\\archivedir\\%f" "%p"' # Windows Specifies the maximum number of replication slots (see ) that the server - can support. The default is 10. This parameter can only be set at - server start. + can support. This parameter can only be set at server start. Setting it to a lower value than the number of currently existing replication slots will prevent the server from starting. Also, wal_level must be set @@ -4530,7 +4468,7 @@ restore_command = 'copy "C:\\server\\archivedir\\%f" "%p"' # Windows - wal_keep_size (integer) + wal_keep_size (integer) - default is 0 wal_keep_size configuration parameter @@ -4554,7 +4492,7 @@ restore_command = 'copy "C:\\server\\archivedir\\%f" "%p"' # Windows This sets only the minimum size of segments retained in pg_wal; the system might need to retain more segments for WAL archival or to recover from a checkpoint. If - wal_keep_size is zero (the default), the system + Using value wal_keep_size, the system doesn't keep any extra segments for standby purposes, so the number of old WAL segments available to standby servers is a function of the location of the previous checkpoint and status of WAL @@ -4567,7 +4505,7 @@ restore_command = 'copy "C:\\server\\archivedir\\%f" "%p"' # Windows - max_slot_wal_keep_size (integer) + max_slot_wal_keep_size (integer) - default is -1 max_slot_wal_keep_size configuration parameter @@ -4578,7 +4516,7 @@ restore_command = 'copy "C:\\server\\archivedir\\%f" "%p"' # Windows that replication slots are allowed to retain in the pg_wal directory at checkpoint time. - If max_slot_wal_keep_size is -1 (the default), + If max_slot_wal_keep_size is set to -1, replication slots may retain an unlimited amount of WAL files. Otherwise, if restart_lsn of a replication slot falls behind the current LSN by more than the given size, the standby using the slot may no longer be able @@ -4633,7 +4571,7 @@ restore_command = 'copy "C:\\server\\archivedir\\%f" "%p"' # Windows - wal_sender_timeout (integer) + wal_sender_timeout (integer) - default is 60 seconds wal_sender_timeout configuration parameter @@ -4644,7 +4582,6 @@ restore_command = 'copy "C:\\server\\archivedir\\%f" "%p"' # Windows than this amount of time. This is useful for the sending server to detect a standby crash or network outage. If this value is specified without units, it is taken as milliseconds. - The default value is 60 seconds. A value of zero disables the timeout mechanism. @@ -4660,7 +4597,7 @@ restore_command = 'copy "C:\\server\\archivedir\\%f" "%p"' # Windows - track_commit_timestamp (boolean) + track_commit_timestamp (boolean) - default is off track_commit_timestamp configuration parameter @@ -4669,13 +4606,13 @@ restore_command = 'copy "C:\\server\\archivedir\\%f" "%p"' # Windows Record commit time of transactions. This parameter can only be set in postgresql.conf file or on the server - command line. The default value is off. + command line. - synchronized_standby_slots (string) + synchronized_standby_slots (string) - default is '' synchronized_standby_slots configuration parameter @@ -4734,7 +4671,7 @@ restore_command = 'copy "C:\\server\\archivedir\\%f" "%p"' # Windows - synchronous_standby_names (string) + synchronous_standby_names (string) - default is '' synchronous_standby_names configuration parameter @@ -4880,7 +4817,7 @@ ANY num_sync ( - primary_conninfo (string) + primary_conninfo (string) - default is '' primary_conninfo configuration parameter @@ -4950,7 +4887,7 @@ ANY num_sync ( - hot_standby (boolean) + hot_standby (boolean) - default is on hot_standby configuration parameter @@ -4959,7 +4896,6 @@ ANY num_sync ( . - The default value is on. This parameter can only be set at server start. It only has effect during archive recovery or in standby mode. @@ -4967,7 +4903,7 @@ ANY num_sync ( - max_standby_archive_delay (integer) + max_standby_archive_delay (integer) - default is 30 seconds max_standby_archive_delay configuration parameter @@ -4981,7 +4917,6 @@ ANY num_sync ( num_sync ( - max_standby_streaming_delay (integer) + max_standby_streaming_delay (integer) - default is 30 seconds max_standby_streaming_delay configuration parameter @@ -5013,7 +4948,6 @@ ANY num_sync ( num_sync ( - wal_receiver_create_temp_slot (boolean) + wal_receiver_create_temp_slot (boolean) - default is off wal_receiver_create_temp_slot configuration parameter @@ -5042,7 +4976,7 @@ ANY num_sync ( ). - The default is off. This parameter can only be set in the + This parameter can only be set in the postgresql.conf file or on the server command line. If this parameter is changed while the WAL receiver process is running, that process is signaled to shut down and expected to restart with @@ -5052,7 +4986,7 @@ ANY num_sync ( - wal_receiver_status_interval (integer) + wal_receiver_status_interval (integer) - default is 10 seconds wal_receiver_status_interval configuration parameter @@ -5076,15 +5010,14 @@ ANY num_sync ( - hot_standby_feedback (boolean) + hot_standby_feedback (boolean) - default is off hot_standby_feedback configuration parameter @@ -5097,8 +5030,7 @@ ANY num_sync ( ( - wal_receiver_timeout (integer) + wal_receiver_timeout (integer) - default is 60 seconds wal_receiver_timeout configuration parameter @@ -5129,7 +5061,6 @@ ANY num_sync ( num_sync ( - wal_retrieve_retry_interval (integer) + wal_retrieve_retry_interval (integer) - default is 5 seconds wal_retrieve_retry_interval configuration parameter @@ -5151,7 +5082,6 @@ ANY num_sync ( num_sync ( - recovery_min_apply_delay (integer) + recovery_min_apply_delay (integer) - default is 0 recovery_min_apply_delay configuration parameter @@ -5192,7 +5122,7 @@ ANY num_sync ( num_sync ( - sync_replication_slots (boolean) + sync_replication_slots (boolean) - default is off sync_replication_slots configuration parameter @@ -5259,7 +5189,7 @@ ANY num_sync ( num_sync ( - max_active_replication_origins (integer) + max_active_replication_origins (integer) - default is 10 max_active_replication_origins configuration parameter @@ -5303,7 +5233,7 @@ ANY num_sync ( - max_logical_replication_workers (integer) + max_logical_replication_workers (integer) - default is 4 max_logical_replication_workers configuration parameter @@ -5319,14 +5249,13 @@ ANY num_sync ( - max_sync_workers_per_subscription (integer) + max_sync_workers_per_subscription (integer) - default is 2 max_sync_workers_per_subscription configuration parameter @@ -5345,15 +5274,13 @@ ANY num_sync ( - max_parallel_apply_workers_per_subscription (integer) + max_parallel_apply_workers_per_subscription (integer) - default is 2 max_parallel_apply_workers_per_subscription configuration parameter @@ -5370,9 +5297,7 @@ ANY num_sync ( num_sync ( - enable_async_append (boolean) + enable_async_append (boolean) - default is on enable_async_append configuration parameter - Enables or disables the query planner's use of async-aware - append plan types. The default is on. + Enables or disables the query planner's use of async-aware append plan types. - enable_bitmapscan (boolean) + enable_bitmapscan (boolean) - default is on bitmap scan @@ -5432,8 +5356,7 @@ ANY num_sync ( num_sync ( - enable_gathermerge (boolean) + enable_gathermerge (boolean) - default is on enable_gathermerge configuration parameter - Enables or disables the query planner's use of gather - merge plan types. The default is on. + Enables or disables the query planner's use of gather merge plan types. - enable_group_by_reordering (boolean) + enable_group_by_reordering (boolean) - default is on enable_group_by_reordering configuration parameter @@ -5479,42 +5401,39 @@ ANY num_sync ( - enable_hashagg (boolean) + enable_hashagg (boolean) - default is on enable_hashagg configuration parameter - Enables or disables the query planner's use of hashed - aggregation plan types. The default is on. + Enables or disables the query planner's use of hashed aggregation plan types. - enable_hashjoin (boolean) + enable_hashjoin (boolean) - default is on enable_hashjoin configuration parameter - Enables or disables the query planner's use of hash-join plan - types. The default is on. + Enables or disables the query planner's use of hash-join plan types. - enable_incremental_sort (boolean) + enable_incremental_sort (boolean) - default is on enable_incremental_sort configuration parameter @@ -5522,13 +5441,12 @@ ANY num_sync ( - enable_indexscan (boolean) + enable_indexscan (boolean) - default is on index scan @@ -5538,15 +5456,14 @@ ANY num_sync ( . - enable_indexonlyscan (boolean) + enable_indexonlyscan (boolean) - default is on enable_indexonlyscan configuration parameter @@ -5555,15 +5472,14 @@ ANY num_sync ( ). - The default is on. The - setting must also be + The setting must also be enabled to have the query planner consider index-only-scans. - enable_material (boolean) + enable_material (boolean) - default is on enable_material configuration parameter @@ -5574,13 +5490,12 @@ ANY num_sync ( - enable_memoize (boolean) + enable_memoize (boolean) - default is on enable_memoize configuration parameter @@ -5592,28 +5507,26 @@ ANY num_sync ( - enable_mergejoin (boolean) + enable_mergejoin (boolean) - default is on enable_mergejoin configuration parameter - Enables or disables the query planner's use of merge-join plan - types. The default is on. + Enables or disables the query planner's use of merge-join plan types. - enable_nestloop (boolean) + enable_nestloop (boolean) - default is on enable_nestloop configuration parameter @@ -5623,28 +5536,26 @@ ANY num_sync ( - enable_parallel_append (boolean) + enable_parallel_append (boolean) - default is on enable_parallel_append configuration parameter - Enables or disables the query planner's use of parallel-aware - append plan types. The default is on. + Enables or disables the query planner's use of parallel-aware append plan types. - enable_parallel_hash (boolean) + enable_parallel_hash (boolean) - default is on enable_parallel_hash configuration parameter @@ -5652,14 +5563,13 @@ ANY num_sync ( - enable_partition_pruning (boolean) + enable_partition_pruning (boolean) - default is on enable_partition_pruning configuration parameter @@ -5669,15 +5579,14 @@ ANY num_sync ( for details. - enable_partitionwise_join (boolean) + enable_partitionwise_join (boolean) - default is on enable_partitionwise_join configuration parameter @@ -5695,13 +5604,13 @@ ANY num_sync ( - enable_partitionwise_aggregate (boolean) + enable_partitionwise_aggregate (boolean) - default is on enable_partitionwise_aggregate configuration parameter @@ -5719,14 +5628,13 @@ ANY num_sync ( - enable_presorted_aggregate (boolean) + enable_presorted_aggregate (boolean) - default is on enable_presorted_aggregate configuration parameter @@ -5742,8 +5650,7 @@ ANY num_sync ( num_sync ( - enable_seqscan (boolean) + enable_seqscan (boolean) - default is on sequential scan @@ -5778,14 +5685,13 @@ ANY num_sync ( - enable_sort (boolean) + enable_sort (boolean) - default is on enable_sort configuration parameter @@ -5795,22 +5701,20 @@ ANY num_sync ( - enable_tidscan (boolean) + enable_tidscan (boolean) - default is on enable_tidscan configuration parameter - Enables or disables the query planner's use of TID - scan plan types. The default is on. + Enables or disables the query planner's use of TID scan plan types. @@ -5845,7 +5749,7 @@ ANY num_sync ( - seq_page_cost (floating point) + seq_page_cost (floating point) - default is 1.0 seq_page_cost configuration parameter @@ -5853,7 +5757,7 @@ ANY num_sync ( ). @@ -5862,7 +5766,7 @@ ANY num_sync ( - random_page_cost (floating point) + random_page_cost (floating point) - default is 4.0 random_page_cost configuration parameter @@ -5870,7 +5774,7 @@ ANY num_sync ( ). @@ -5887,8 +5791,8 @@ ANY num_sync ( num_sync ( - cpu_tuple_cost (floating point) + cpu_tuple_cost (floating point) - default is 0.01 cpu_tuple_cost configuration parameter @@ -5931,13 +5835,12 @@ ANY num_sync ( - cpu_index_tuple_cost (floating point) + cpu_index_tuple_cost (floating point) - default is 0.005 cpu_index_tuple_cost configuration parameter @@ -5946,13 +5849,12 @@ ANY num_sync ( - cpu_operator_cost (floating point) + cpu_operator_cost (floating point) - default is 0.0025 cpu_operator_cost configuration parameter @@ -5961,28 +5863,25 @@ ANY num_sync ( - parallel_setup_cost (floating point) + parallel_setup_cost (floating point) - default is 1000 parallel_setup_cost configuration parameter - Sets the planner's estimate of the cost of launching parallel worker - processes. - The default is 1000. + Sets the planner's estimate of the cost of launching parallel worker processes. - parallel_tuple_cost (floating point) + parallel_tuple_cost (floating point) - default is 0.1 parallel_tuple_cost configuration parameter @@ -5991,13 +5890,12 @@ ANY num_sync ( - min_parallel_table_scan_size (integer) + min_parallel_table_scan_size (integer) - default is 8MB min_parallel_table_scan_size configuration parameter @@ -6011,13 +5909,12 @@ ANY num_sync ( - min_parallel_index_scan_size (integer) + min_parallel_index_scan_size (integer) - default is 512kb min_parallel_index_scan_size configuration parameter @@ -6033,13 +5930,12 @@ ANY num_sync ( . If this value is specified without units, it is taken as blocks, that is BLCKSZ bytes, typically 8kB. - The default is 512 kilobytes (512kB). - effective_cache_size (integer) + effective_cache_size (integer) - default is 4GB effective_cache_size configuration parameter @@ -6065,7 +5961,6 @@ ANY num_sync ( num_sync ( - jit_above_cost (floating point) + jit_above_cost (floating point) - default is 100000 jit_above_cost configuration parameter @@ -6085,13 +5980,12 @@ ANY num_sync ( - jit_inline_above_cost (floating point) + jit_inline_above_cost (floating point) - default is 500000 jit_inline_above_cost configuration parameter @@ -6103,13 +5997,12 @@ ANY num_sync ( - jit_optimize_above_cost (floating point) + jit_optimize_above_cost (floating point) - default is 500000 jit_optimize_above_cost configuration parameter @@ -6123,7 +6016,6 @@ ANY num_sync ( num_sync ( - geqo (boolean) + geqo (boolean) - default is on genetic query optimization @@ -6161,7 +6053,7 @@ ANY num_sync ( num_sync ( - geqo_threshold (integer) + geqo_threshold (integer) - default is 12 geqo_threshold configuration parameter @@ -6179,7 +6071,7 @@ ANY num_sync ( num_sync ( - geqo_effort (integer) + geqo_effort (integer) - default is 5 geqo_effort configuration parameter @@ -6199,7 +6091,7 @@ ANY num_sync ( num_sync ( - geqo_pool_size (integer) + geqo_pool_size (integer) - default is 0 geqo_pool_size configuration parameter @@ -6226,7 +6118,7 @@ ANY num_sync ( num_sync ( - geqo_generations (integer) + geqo_generations (integer) - default is 0 geqo_generations configuration parameter @@ -6244,15 +6136,14 @@ ANY num_sync ( - geqo_selection_bias (floating point) + geqo_selection_bias (floating point) - default is 2.00 geqo_selection_bias configuration parameter @@ -6261,13 +6152,13 @@ ANY num_sync ( - geqo_seed (floating point) + geqo_seed (floating point) - default is 0 geqo_seed configuration parameter @@ -6276,7 +6167,7 @@ ANY num_sync ( num_sync ( - default_statistics_target (integer) + default_statistics_target (integer) - default is 100 default_statistics_target configuration parameter @@ -6302,7 +6193,7 @@ ANY num_sync ( . @@ -6310,7 +6201,7 @@ ANY num_sync ( - constraint_exclusion (enum) + constraint_exclusion (enum) - default is partition constraint exclusion @@ -6327,7 +6218,6 @@ ANY num_sync ( - cursor_tuple_fraction (floating point) + cursor_tuple_fraction (floating point) - default is 0.1 cursor_tuple_fraction configuration parameter @@ -6379,7 +6269,7 @@ SELECT * FROM parent WHERE key = 2400; Sets the planner's estimate of the fraction of a cursor's rows that - will be retrieved. The default is 0.1. Smaller values of this + will be retrieved. Smaller values of this setting bias the planner towards using fast start plans for cursors, which will retrieve the first few rows quickly while perhaps taking a long time to fetch all rows. Larger values @@ -6392,7 +6282,7 @@ SELECT * FROM parent WHERE key = 2400; - from_collapse_limit (integer) + from_collapse_limit (integer) - default is 8 from_collapse_limit configuration parameter @@ -6402,7 +6292,7 @@ SELECT * FROM parent WHERE key = 2400; The planner will merge sub-queries into upper queries if the resulting FROM list would have no more than this many items. Smaller values reduce planning time but might - yield inferior query plans. The default is eight. + yield inferior query plans. For more information see . @@ -6415,7 +6305,7 @@ SELECT * FROM parent WHERE key = 2400; - jit (boolean) + jit (boolean) - default is on jit configuration parameter @@ -6425,13 +6315,12 @@ SELECT * FROM parent WHERE key = 2400; Determines whether JIT compilation may be used by PostgreSQL, if available (see ). - The default is on. - join_collapse_limit (integer) + join_collapse_limit (integer) - default is the same as from_collapse_limit join_collapse_limit configuration parameter @@ -6446,8 +6335,7 @@ SELECT * FROM parent WHERE key = 2400; - By default, this variable is set the same as - from_collapse_limit, which is appropriate + Being this value the same as from_collapse_limit is appropriate for most uses. Setting it to 1 prevents any reordering of explicit JOINs. Thus, the explicit join order specified in the query will be the actual order in which the @@ -6467,7 +6355,7 @@ SELECT * FROM parent WHERE key = 2400; - plan_cache_mode (enum) + plan_cache_mode (enum) - default is auto plan_cache_mode configuration parameter @@ -6484,7 +6372,7 @@ SELECT * FROM parent WHERE key = 2400; generic plan may be inefficient. The choice between these options is normally made automatically, but it can be overridden with plan_cache_mode. - The allowed values are auto (the default), + The allowed values are auto, force_custom_plan and force_generic_plan. This setting is considered when a cached plan is to be executed, @@ -6495,7 +6383,7 @@ SELECT * FROM parent WHERE key = 2400; - recursive_worktable_factor (floating point) + recursive_worktable_factor (floating point) - default is 10.0 recursive_worktable_factor configuration parameter @@ -6508,8 +6396,7 @@ SELECT * FROM parent WHERE key = 2400; non-recursive term of the query. This helps the planner choose the most appropriate method for joining the working table to the query's other tables. - The default value is 10.0. A smaller value - such as 1.0 can be helpful when the recursion + A smaller value than the default, such as 1.0, can be helpful when the recursion has low fan-out from one step to the next, as for example in shortest-path queries. Graph analytics queries may benefit from larger-than-default values. @@ -6543,7 +6430,7 @@ SELECT * FROM parent WHERE key = 2400; - log_destination (string) + log_destination (string) - default is stderr log_destination configuration parameter @@ -6557,8 +6444,7 @@ SELECT * FROM parent WHERE key = 2400; syslog. On Windows, eventlog is also supported. Set this parameter to a list of desired log destinations separated by - commas. The default is to log to stderr - only. + commas. This parameter can only be set in the postgresql.conf file or on the server command line. @@ -6633,7 +6519,7 @@ local0.* /var/log/postgresql - logging_collector (boolean) + logging_collector (boolean) - default is off logging_collector configuration parameter @@ -6680,7 +6566,7 @@ local0.* /var/log/postgresql - log_directory (string) + log_directory (string) - default is log log_directory configuration parameter @@ -6693,13 +6579,12 @@ local0.* /var/log/postgresql cluster data directory. This parameter can only be set in the postgresql.conf file or on the server command line. - The default is log. - log_filename (string) + log_filename (string) - default is postgresql-%Y-%m-%d_%H%M%S.log log_filename configuration parameter @@ -6720,7 +6605,6 @@ local0.* /var/log/postgresql specification. Note that the system's strftime is not used directly, so platform-specific (nonstandard) extensions do not work. - The default is postgresql-%Y-%m-%d_%H%M%S.log. If you specify a file name without escapes, you should plan to @@ -6753,7 +6637,7 @@ local0.* /var/log/postgresql - log_file_mode (integer) + log_file_mode (integer) - default is 0600 log_file_mode configuration parameter @@ -6770,7 +6654,7 @@ local0.* /var/log/postgresql must start with a 0 (zero).) - The default permissions are 0600, meaning only the + Value of 0600, meaning only the server owner can read or write the log files. The other commonly useful setting is 0640, allowing members of the owner's group to read the files. Note however that to make use of such a @@ -6787,7 +6671,7 @@ local0.* /var/log/postgresql - log_rotation_age (integer) + log_rotation_age (integer) - default is 24hours log_rotation_age configuration parameter @@ -6798,7 +6682,6 @@ local0.* /var/log/postgresql this parameter determines the maximum amount of time to use an individual log file, after which a new log file will be created. If this value is specified without units, it is taken as minutes. - The default is 24 hours. Set to zero to disable time-based creation of new log files. This parameter can only be set in the postgresql.conf file or on the server command line. @@ -6807,7 +6690,7 @@ local0.* /var/log/postgresql - log_rotation_size (integer) + log_rotation_size (integer) - default is 10MB log_rotation_size configuration parameter @@ -6819,7 +6702,6 @@ local0.* /var/log/postgresql After this amount of data has been emitted into a log file, a new log file will be created. If this value is specified without units, it is taken as kilobytes. - The default is 10 megabytes. Set to zero to disable size-based creation of new log files. This parameter can only be set in the postgresql.conf file or on the server command line. @@ -6828,7 +6710,7 @@ local0.* /var/log/postgresql - log_truncate_on_rotation (boolean) + log_truncate_on_rotation (boolean) - default is off log_truncate_on_rotation configuration parameter @@ -6871,7 +6753,7 @@ local0.* /var/log/postgresql - syslog_facility (enum) + syslog_facility (enum) - default is LOCAL0 syslog_facility configuration parameter @@ -6884,9 +6766,7 @@ local0.* /var/log/postgresql from LOCAL0, LOCAL1, LOCAL2, LOCAL3, LOCAL4, LOCAL5, LOCAL6, LOCAL7; - the default is LOCAL0. See also the - documentation of your system's - syslog daemon. + See also the documentation of your system's syslog daemon. This parameter can only be set in the postgresql.conf file or on the server command line. @@ -6894,7 +6774,7 @@ local0.* /var/log/postgresql - syslog_ident (string) + syslog_ident (string) - default is postgres syslog_ident configuration parameter @@ -6904,8 +6784,7 @@ local0.* /var/log/postgresql When logging to syslog is enabled, this parameter determines the program name used to identify PostgreSQL messages in - syslog logs. The default is - postgres. + syslog logs. This parameter can only be set in the postgresql.conf file or on the server command line. @@ -6913,7 +6792,7 @@ local0.* /var/log/postgresql - syslog_sequence_numbers (boolean) + syslog_sequence_numbers (boolean) - default is on syslog_sequence_numbers configuration parameter @@ -6921,8 +6800,8 @@ local0.* /var/log/postgresql - When logging to syslog and this is on (the - default), then each message will be prefixed by an increasing + When logging to syslog and this is on, + then each message will be prefixed by an increasing sequence number (such as [2]). This circumvents the --- last message repeated N times --- suppression that many syslog implementations perform by default. In more modern @@ -6941,7 +6820,7 @@ local0.* /var/log/postgresql - syslog_split_messages (boolean) + syslog_split_messages (boolean) - default is on syslog_split_messages configuration parameter @@ -6949,8 +6828,8 @@ local0.* /var/log/postgresql When logging to syslog is enabled, this parameter - determines how messages are delivered to syslog. When on (the - default), messages are split by lines, and long lines are split so + determines how messages are delivered to syslog. When this value is on, + messages are split by lines, and long lines are split so that they will fit into 1024 bytes, which is a typical size limit for traditional syslog implementations. When off, PostgreSQL server log messages are delivered to the syslog service as is, and it is up to @@ -6974,7 +6853,7 @@ local0.* /var/log/postgresql - event_source (string) + event_source (string) - default is PostgreSQL event_source configuration parameter @@ -6984,7 +6863,7 @@ local0.* /var/log/postgresql When logging to event log is enabled, this parameter determines the program name used to identify PostgreSQL messages in - the log. The default is PostgreSQL. + the log. This parameter can only be set in the postgresql.conf file or on the server command line. @@ -6999,7 +6878,7 @@ local0.* /var/log/postgresql - log_min_messages (enum) + log_min_messages (enum) - default is WARNING log_min_messages configuration parameter @@ -7014,8 +6893,7 @@ local0.* /var/log/postgresql ERROR, LOG, FATAL, and PANIC. Each level includes all the levels that follow it. The later the level, the fewer messages are sent - to the log. The default is WARNING. Note that - LOG has a different rank here than in + to the log. Note that LOG has a different rank here than in . Only superusers and users with the appropriate SET privilege can change this setting. @@ -7024,7 +6902,7 @@ local0.* /var/log/postgresql - log_min_error_statement (enum) + log_min_error_statement (enum) - default is ERROR log_min_error_statement configuration parameter @@ -7044,7 +6922,7 @@ local0.* /var/log/postgresql WARNING, ERROR, LOG, FATAL, and PANIC. - The default is ERROR, which means statements + Using ERROR, which means statements causing errors, log messages, fatal errors, or panics will be logged. To effectively turn off logging of failing statements, set this parameter to PANIC. @@ -7055,7 +6933,7 @@ local0.* /var/log/postgresql - log_min_duration_statement (integer) + log_min_duration_statement (integer) - default is -1 log_min_duration_statement configuration parameter @@ -7070,8 +6948,7 @@ local0.* /var/log/postgresql unoptimized queries in your applications. If this value is specified without units, it is taken as milliseconds. Setting this to zero prints all statement durations. - -1 (the default) disables logging statement - durations. + -1 disables logging statement durations. Only superusers and users with the appropriate SET privilege can change this setting. @@ -7105,7 +6982,7 @@ local0.* /var/log/postgresql - log_min_duration_sample (integer) + log_min_duration_sample (integer) - default is -1 log_min_duration_sample configuration parameter @@ -7124,8 +7001,7 @@ local0.* /var/log/postgresql traffic is too high to log all queries. If this value is specified without units, it is taken as milliseconds. Setting this to zero samples all statement durations. - -1 (the default) disables sampling statement - durations. + -1 disables sampling statement durations. Only superusers and users with the appropriate SET privilege can change this setting. @@ -7146,7 +7022,7 @@ local0.* /var/log/postgresql - log_statement_sample_rate (floating point) + log_statement_sample_rate (floating point) - default is 1.0 log_statement_sample_rate configuration parameter @@ -7158,7 +7034,7 @@ local0.* /var/log/postgresql Sampling is stochastic, for example 0.5 means there is statistically one chance in two that any given statement will be logged. - The default is 1.0, meaning to log all sampled + Value of 1.0, meaning to log all sampled statements. Setting this to zero disables sampled statement-duration logging, the same as setting @@ -7171,7 +7047,7 @@ local0.* /var/log/postgresql - log_transaction_sample_rate (floating point) + log_transaction_sample_rate (floating point) - default is 0 log_transaction_sample_rate configuration parameter @@ -7186,7 +7062,7 @@ local0.* /var/log/postgresql will be logged. log_transaction_sample_rate can be helpful to construct a sample of transactions. - The default is 0, meaning not to log + If this value is set to 0 means not to log statements from any additional transactions. Setting this to 1 logs all statements of all transactions. Only superusers and users with the appropriate SET @@ -7202,7 +7078,7 @@ local0.* /var/log/postgresql - log_startup_progress_interval (integer) + log_startup_progress_interval (integer) - default is 10 seconds log_startup_progress_interval configuration parameter @@ -7212,7 +7088,7 @@ local0.* /var/log/postgresql Sets the amount of time after which the startup process will log a message about a long-running operation that is still in progress, as well as the interval between further progress messages for that - operation. The default is 10 seconds. A setting of 0 + operation. A setting of 0 disables the feature. If this value is specified without units, it is taken as milliseconds. This setting is applied separately to each operation. @@ -7223,7 +7099,7 @@ local0.* /var/log/postgresql For example, if syncing the data directory takes 25 seconds and thereafter resetting unlogged relations takes 8 seconds, and if this - setting has the default value of 10 seconds, then a messages will be + value is set to 10 seconds, then a messages will be logged for syncing the data directory after it has been in progress for 10 seconds and again after it has been in progress for 20 seconds, but nothing will be logged for resetting unlogged relations. @@ -7360,17 +7236,17 @@ local0.* /var/log/postgresql - debug_print_parse (boolean) + debug_print_parse (boolean) - default is off debug_print_parse configuration parameter - debug_print_rewritten (boolean) + debug_print_rewritten (boolean) - default is off debug_print_rewritten configuration parameter - debug_print_plan (boolean) + debug_print_plan (boolean) - default is off debug_print_plan configuration parameter @@ -7385,13 +7261,12 @@ local0.* /var/log/postgresql client. You can change that by adjusting and/or . - These parameters are off by default. - debug_pretty_print (boolean) + debug_pretty_print (boolean) - default is on debug_pretty_print configuration parameter @@ -7403,13 +7278,13 @@ local0.* /var/log/postgresql debug_print_rewritten, or debug_print_plan. This results in more readable but much longer output than the compact format used when - it is off. It is on by default. + it is off. - log_autovacuum_min_duration (integer) + log_autovacuum_min_duration (integer) - default is 10 minutes log_autovacuum_min_duration configuration parameter @@ -7426,7 +7301,7 @@ local0.* /var/log/postgresql 250ms or longer will be logged. In addition, when this parameter is set to any value other than -1, a message will be logged if an autovacuum action is skipped due to a conflicting lock or a - concurrently dropped relation. The default is 10min. + concurrently dropped relation. Enabling this parameter can be helpful in tracking autovacuum activity. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for @@ -7436,7 +7311,7 @@ local0.* /var/log/postgresql - log_checkpoints (boolean) + log_checkpoints (boolean) - default is on log_checkpoints configuration parameter @@ -7447,13 +7322,13 @@ local0.* /var/log/postgresql Some statistics are included in the log messages, including the number of buffers written and the time spent writing them. This parameter can only be set in the postgresql.conf - file or on the server command line. The default is on. + file or on the server command line. - log_connections (string) + log_connections (boolean) - default is off log_connections configuration parameter @@ -7566,7 +7441,7 @@ local0.* /var/log/postgresql - log_disconnections (boolean) + log_disconnections (boolean) - default is off log_disconnections configuration parameter @@ -7579,14 +7454,13 @@ local0.* /var/log/postgresql Only superusers and users with the appropriate SET privilege can change this parameter at session start, and it cannot be changed at all within a session. - The default is off. - log_duration (boolean) + log_duration (boolean) - default is off log_duration configuration parameter @@ -7594,7 +7468,6 @@ local0.* /var/log/postgresql Causes the duration of every completed statement to be logged. - The default is off. Only superusers and users with the appropriate SET privilege can change this setting. @@ -7621,7 +7494,7 @@ local0.* /var/log/postgresql - log_error_verbosity (enum) + log_error_verbosity (enum) - default is DEFAULT log_error_verbosity configuration parameter @@ -7644,7 +7517,7 @@ local0.* /var/log/postgresql - log_hostname (boolean) + log_hostname (boolean) - default is off log_hostname configuration parameter @@ -7662,7 +7535,7 @@ local0.* /var/log/postgresql - log_line_prefix (string) + log_line_prefix (string) - default is %m [%p] %q%u@%d log_line_prefix configuration parameter @@ -7687,8 +7560,8 @@ local0.* /var/log/postgresql This parameter can only be set in the postgresql.conf - file or on the server command line. The default is - '%m [%p] ' which logs a time stamp and the process ID. + file or on the server command line. If this value is set to its default then + log will have a time stamp and the process ID. @@ -7890,7 +7763,7 @@ log_line_prefix = '%m [%p] %q%u@%d/%a ' - log_lock_waits (boolean) + log_lock_waits (boolean) - default is off log_lock_waits configuration parameter @@ -7900,7 +7773,7 @@ log_line_prefix = '%m [%p] %q%u@%d/%a ' Controls whether a log message is produced when a session waits longer than to acquire a lock. This is useful in determining if lock waits are causing - poor performance. The default is off. + poor performance. Only superusers and users with the appropriate SET privilege can change this setting. @@ -7928,7 +7801,7 @@ log_line_prefix = '%m [%p] %q%u@%d/%a ' - log_recovery_conflict_waits (boolean) + log_recovery_conflict_waits (boolean) - default is off log_recovery_conflict_waits configuration parameter @@ -7942,7 +7815,7 @@ log_line_prefix = '%m [%p] %q%u@%d/%a ' - The default is off. This parameter can only be set + This parameter can only be set in the postgresql.conf file or on the server command line. @@ -7950,7 +7823,7 @@ log_line_prefix = '%m [%p] %q%u@%d/%a ' - log_parameter_max_length (integer) + log_parameter_max_length (integer) - default is -1 log_parameter_max_length configuration parameter @@ -7960,7 +7833,7 @@ log_line_prefix = '%m [%p] %q%u@%d/%a ' If greater than zero, each bind parameter value logged with a non-error statement-logging message is trimmed to this many bytes. Zero disables logging of bind parameters for non-error statement logs. - -1 (the default) allows bind parameters to be + Value of -1 allows bind parameters to be logged in full. If this value is specified without units, it is taken as bytes. Only superusers and users with the appropriate SET @@ -7978,7 +7851,7 @@ log_line_prefix = '%m [%p] %q%u@%d/%a ' - log_parameter_max_length_on_error (integer) + log_parameter_max_length_on_error (integer) - default is 0 log_parameter_max_length_on_error configuration parameter @@ -7987,8 +7860,7 @@ log_line_prefix = '%m [%p] %q%u@%d/%a ' If greater than zero, each bind parameter value reported in error messages is trimmed to this many bytes. - Zero (the default) disables including bind parameters in error - messages. + Value of 0 disables including bind parameters in error messages. -1 allows bind parameters to be printed in full. If this value is specified without units, it is taken as bytes. @@ -8006,7 +7878,7 @@ log_line_prefix = '%m [%p] %q%u@%d/%a ' - log_statement (enum) + log_statement (enum) - default is none log_statement configuration parameter @@ -8031,7 +7903,6 @@ log_line_prefix = '%m [%p] %q%u@%d/%a ' - The default is none. Only superusers and users with the appropriate SET privilege can change this setting. @@ -8056,7 +7927,7 @@ log_line_prefix = '%m [%p] %q%u@%d/%a ' - log_replication_commands (boolean) + log_replication_commands (boolean) - default is off log_replication_commands configuration parameter @@ -8066,15 +7937,14 @@ log_line_prefix = '%m [%p] %q%u@%d/%a ' Causes each replication command and walsender process's replication slot acquisition/release to be logged in the server log. See for more - information about replication command. The default value is - off. Only superusers and users with the appropriate + information about replication command. Only superusers and users with the appropriate SET privilege can change this setting. - log_temp_files (integer) + log_temp_files (integer) - default is -1 log_temp_files configuration parameter @@ -8090,7 +7960,7 @@ log_line_prefix = '%m [%p] %q%u@%d/%a ' values log only files whose size is greater than or equal to the specified amount of data. If this value is specified without units, it is taken as kilobytes. - The default setting is -1, which disables such logging. + Setting this value to -1 disables such logging. Only superusers and users with the appropriate SET privilege can change this setting. @@ -8098,7 +7968,7 @@ log_line_prefix = '%m [%p] %q%u@%d/%a ' - log_timezone (string) + log_timezone (string) - default is GMT log_timezone configuration parameter @@ -8119,7 +7989,7 @@ log_line_prefix = '%m [%p] %q%u@%d/%a ' - md5_password_warnings (boolean) + md5_password_warnings (boolean) - default is on md5_password_warnings configuration parameter @@ -8129,7 +7999,6 @@ log_line_prefix = '%m [%p] %q%u@%d/%a ' Controls whether a WARNING about MD5 password deprecation is produced when a CREATE ROLE or ALTER ROLE statement sets an MD5-encrypted password. - The default value is on. @@ -8460,7 +8329,7 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv; - cluster_name (string) + cluster_name (string) - default is '' cluster_name configuration parameter @@ -8481,15 +8350,14 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv; cluster_name value. Other characters are replaced with C-style hexadecimal escapes. - No name is shown if this parameter is set to the empty string - '' (which is the default). + No name is shown if this parameter is set to an empty string. This parameter can only be set at server start. - update_process_title (boolean) + update_process_title (boolean) - default is on on Windows, otherwise off update_process_title configuration parameter @@ -8498,7 +8366,7 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv; Enables updating of the process title every time a new SQL command is received by the server. - This setting defaults to on on most platforms, but it + Usual value is on on most platforms, but it defaults to off on Windows due to that platform's larger overhead for updating the process title. Only superusers and users with the appropriate SET @@ -8527,7 +8395,7 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv; - track_activities (boolean) + track_activities (boolean) - default is on track_activities configuration parameter @@ -8536,8 +8404,7 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv; Enables the collection of information on the currently executing command of each session, along with its identifier and the - time when that command began execution. This parameter is on by - default. Note that even when enabled, this information is only + time when that command began execution. Note that even when enabled, this information is only visible to superusers, roles with privileges of the pg_read_all_stats role and the user owning the sessions being reported on (including sessions belonging to a role they @@ -8549,7 +8416,7 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv; - track_activity_query_size (integer) + track_activity_query_size (integer) - default is 1024 bytes track_activity_query_size configuration parameter @@ -8560,14 +8427,13 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv; currently executing command for each active session, for the pg_stat_activity.query field. If this value is specified without units, it is taken as bytes. - The default value is 1024 bytes. This parameter can only be set at server start. - track_counts (boolean) + track_counts (boolean) - default is on track_counts configuration parameter @@ -8575,7 +8441,7 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv; Enables collection of statistics on database activity. - This parameter is on by default, because the autovacuum + This parameter is usually on because the autovacuum daemon needs the collected information. Only superusers and users with the appropriate SET privilege can change this setting. @@ -8584,7 +8450,7 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv; - track_cost_delay_timing (boolean) + track_cost_delay_timing (boolean) - default is off track_cost_delay_timing configuration parameter @@ -8592,8 +8458,8 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv; Enables timing of cost-based vacuum delay (see - ). This parameter - is off by default, as it will repeatedly query the operating system for + ). If it's set to off, + as it will repeatedly query the operating system for the current time, which may cause significant overhead on some platforms. You can use the tool to measure the overhead of timing on your system. Cost-based vacuum delay @@ -8611,15 +8477,15 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv; - track_io_timing (boolean) + track_io_timing (boolean) - default is off track_io_timing configuration parameter - Enables timing of database I/O waits. This parameter is off by - default, as it will repeatedly query the operating system for + Enables timing of database I/O waits. If it's set to off, + as it will repeatedly query the operating system for the current time, which may cause significant overhead on some platforms. You can use the tool to measure the overhead of timing on your system. @@ -8645,15 +8511,15 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv; - track_wal_io_timing (boolean) + track_wal_io_timing (boolean) - default is none track_wal_io_timing configuration parameter - Enables timing of WAL I/O waits. This parameter is off by default, - as it will repeatedly query the operating system for the current time, + Enables timing of WAL I/O waits. If default is used, + it will repeatedly query the operating system for the current time, which may cause significant overhead on some platforms. You can use the pg_test_timing tool to measure the overhead of timing on your system. @@ -8671,7 +8537,7 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv; - track_functions (enum) + track_functions (enum) - default is none track_functions configuration parameter @@ -8681,7 +8547,7 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv; Enables tracking of function call counts and time used. Specify pl to track only procedural-language functions, all to also track SQL and C language functions. - The default is none, which disables function + If none is used, which disables function statistics tracking. Only superusers and users with the appropriate SET privilege can change this setting. @@ -8698,7 +8564,7 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv; - stats_fetch_consistency (enum) + stats_fetch_consistency (enum) - default is cache stats_fetch_consistency configuration parameter @@ -8716,7 +8582,6 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv; the end of the transaction unless pg_stat_clear_snapshot() is called. Changing this parameter in a transaction discards the statistics snapshot. - The default is cache. @@ -8740,7 +8605,7 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv; - compute_query_id (enum) + compute_query_id (enum) - default is auto compute_query_id configuration parameter @@ -8764,7 +8629,6 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv; has the same effect as auto, except that the query identifier is not shown in the EXPLAIN output in order to facilitate automated regression testing. - The default is auto. @@ -8776,23 +8640,53 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv; + + query_id_squash_values (bool) + + query_id_squash_values configuration parameter + + + + + Specifies how a list of constants (e.g., for an IN + clause) contributes to the query identifier computation. + Normally, every element of such a list contributes to the query + identifier separately, which means that two queries that only differ + in the number of elements in such a list would get different query + identifiers. + If this parameter is on, a list of constants will not contribute + to the query identifier. This means that two queries whose only + difference is the number of constants in such a list are going to get the + same query identifier. + + + Only constants are affected; bind parameters do not benefit from this + functionality. The default value is off. + + + This parameter also affects how + generates normalized query texts. + + + + - log_statement_stats (boolean) + log_statement_stats (boolean) - default is off log_statement_stats configuration parameter - log_parser_stats (boolean) + log_parser_stats (boolean) - default is off log_parser_stats configuration parameter - log_planner_stats (boolean) + log_planner_stats (boolean) - default is off log_planner_stats configuration parameter - log_executor_stats (boolean) + log_executor_stats (boolean) - default is off log_executor_stats configuration parameter @@ -8805,8 +8699,7 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv; system facility. log_statement_stats reports total statement statistics, while the others report per-module statistics. log_statement_stats cannot be enabled together with - any of the per-module options. All of these options are disabled by - default. + any of the per-module options. Only superusers and users with the appropriate SET privilege can change these settings. @@ -8844,7 +8737,7 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv; - autovacuum (boolean) + autovacuum (boolean) - default is on autovacuum configuration parameter @@ -8852,7 +8745,7 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv; Controls whether the server should run the - autovacuum launcher daemon. This is on by default; however, + autovacuum launcher daemon. Even if this is on, must also be enabled for autovacuum to work. This parameter can only be set in the postgresql.conf @@ -8889,7 +8782,7 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv; - autovacuum_max_workers (integer) + autovacuum_max_workers (integer) - default is 3 autovacuum_max_workers configuration parameter @@ -8911,7 +8804,7 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv; - autovacuum_naptime (integer) + autovacuum_naptime (integer) - default is 1 minute autovacuum_naptime configuration parameter @@ -8923,7 +8816,6 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv; database and issues VACUUM and ANALYZE commands as needed for tables in that database. If this value is specified without units, it is taken as seconds. - The default is one minute (1min). This parameter can only be set in the postgresql.conf file or on the server command line. @@ -8931,7 +8823,7 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv; - autovacuum_vacuum_threshold (integer) + autovacuum_vacuum_threshold (integer) - default is 50 tuples autovacuum_vacuum_threshold configuration parameter @@ -8941,7 +8833,6 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv; Specifies the minimum number of updated or deleted tuples needed to trigger a VACUUM in any one table. - The default is 50 tuples. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by @@ -8951,7 +8842,7 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv; - autovacuum_vacuum_insert_threshold (integer) + autovacuum_vacuum_insert_threshold (integer) - default is 1000 tuples autovacuum_vacuum_insert_threshold configuration parameter @@ -8961,7 +8852,7 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv; Specifies the number of inserted tuples needed to trigger a VACUUM in any one table. - The default is 1000 tuples. If -1 is specified, autovacuum will not + If -1 is specified, autovacuum will not trigger a VACUUM operation on any tables based on the number of inserts. This parameter can only be set in the postgresql.conf @@ -8973,7 +8864,7 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv; - autovacuum_analyze_threshold (integer) + autovacuum_analyze_threshold (integer) - default is 50 tuples autovacuum_analyze_threshold configuration parameter @@ -8983,7 +8874,6 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv; Specifies the minimum number of inserted, updated or deleted tuples needed to trigger an ANALYZE in any one table. - The default is 50 tuples. This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by @@ -8993,7 +8883,7 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv; - autovacuum_vacuum_scale_factor (floating point) + autovacuum_vacuum_scale_factor (floating point) - default is 0.2 autovacuum_vacuum_scale_factor configuration parameter @@ -9001,20 +8891,19 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv; - Specifies a fraction of the table size to add to - autovacuum_vacuum_threshold - when deciding whether to trigger a VACUUM. - The default is 0.2 (20% of table size). - This parameter can only be set in the postgresql.conf - file or on the server command line; - but the setting can be overridden for individual tables by - changing table storage parameters. + Specifies a fraction of the unfrozen pages in the table to add to + autovacuum_vacuum_insert_threshold when deciding + whether to trigger a VACUUM. Value of + 0.2 means (20% of unfrozen pages in table). This + parameter can only be set in the postgresql.conf + file or on the server command line; but the setting can be overridden + for individual tables by changing table storage parameters. - autovacuum_vacuum_insert_scale_factor (floating point) + autovacuum_vacuum_insert_scale_factor (floating point) - default is 0.2 autovacuum_vacuum_insert_scale_factor configuration parameter @@ -9024,8 +8913,8 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv; Specifies a fraction of the unfrozen pages in the table to add to autovacuum_vacuum_insert_threshold when deciding - whether to trigger a VACUUM. The default is - 0.2 (20% of unfrozen pages in table). This + whether to trigger a VACUUM. Value of + 0.2 means (20% of unfrozen pages in table). This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by changing table storage parameters. @@ -9034,7 +8923,7 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv; - autovacuum_analyze_scale_factor (floating point) + autovacuum_analyze_scale_factor (floating point) - default is 0.1 autovacuum_analyze_scale_factor configuration parameter @@ -9045,7 +8934,7 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv; Specifies a fraction of the table size to add to autovacuum_analyze_threshold when deciding whether to trigger an ANALYZE. - The default is 0.1 (10% of table size). + Value of 0.1 means (10% of table size). This parameter can only be set in the postgresql.conf file or on the server command line; but the setting can be overridden for individual tables by @@ -9054,30 +8943,6 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv; - - autovacuum_vacuum_max_threshold (integer) - - autovacuum_vacuum_max_threshold - configuration parameter - - - - - Specifies the maximum number of updated or deleted tuples needed to - trigger a VACUUM in any one table, i.e., a limit on - the value calculated with - autovacuum_vacuum_threshold and - autovacuum_vacuum_scale_factor. The default is - 100,000,000 tuples. If -1 is specified, autovacuum will not enforce a - maximum number of updated or deleted tuples that will trigger a - VACUUM operation. This parameter can only be set - in the postgresql.conf file or on the server - command line; but the setting can be overridden for individual tables - by changing storage parameters. - - - - autovacuum_freeze_max_age (integer) @@ -9137,7 +9002,7 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv; - autovacuum_vacuum_cost_delay (floating point) + autovacuum_vacuum_cost_delay (floating point) - default is 2 miliseconds autovacuum_vacuum_cost_delay configuration parameter @@ -9159,7 +9024,7 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv; - autovacuum_vacuum_cost_limit (integer) + autovacuum_vacuum_cost_limit (integer) - default is -1 autovacuum_vacuum_cost_limit configuration parameter @@ -9222,7 +9087,7 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv; - vacuum_cost_delay (floating point) + vacuum_cost_delay (floating point) - default is 0 vacuum_cost_delay configuration parameter @@ -9252,7 +9117,7 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv; - vacuum_cost_page_hit (integer) + vacuum_cost_page_hit (integer) - default is 1 vacuum_cost_page_hit configuration parameter @@ -9268,7 +9133,7 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv; - vacuum_cost_page_miss (integer) + vacuum_cost_page_miss (integer) - default is 2 vacuum_cost_page_miss configuration parameter @@ -9285,7 +9150,7 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv; - vacuum_cost_page_dirty (integer) + vacuum_cost_page_dirty (integer) - default is 20 vacuum_cost_page_dirty configuration parameter @@ -9301,7 +9166,7 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv; - vacuum_cost_limit (integer) + vacuum_cost_limit (integer) - default is 200 vacuum_cost_limit configuration parameter @@ -9309,8 +9174,7 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv; This is the accumulated cost that will cause the vacuuming - process to sleep for vacuum_cost_delay. The - default is 200. + process to sleep for vacuum_cost_delay. @@ -9336,7 +9200,7 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv; - vacuum_truncate (boolean) + vacuum_truncate (boolean) default is true vacuum_truncate configuration parameter @@ -9344,8 +9208,8 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv; Enables or disables vacuum to try to truncate off any empty pages at - the end of the table. The default value is true. - If true, VACUUM and autovacuum + the end of the table. + If true, VACUUM and autovacuum do the truncation and the disk space for the truncated pages is returned to the operating system. Note that the truncation requires an ACCESS EXCLUSIVE lock on the table. The @@ -9378,7 +9242,7 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv; - vacuum_freeze_table_age (integer) + vacuum_freeze_table_age (integer) default is 150 million transactions vacuum_freeze_table_age configuration parameter @@ -9390,7 +9254,7 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv; the age specified by this setting. An aggressive scan differs from a regular VACUUM in that it visits every page that might contain unfrozen XIDs or MXIDs, not just those that might contain dead - tuples. The default is 150 million transactions. Although users can + tuples. Although users can set this value anywhere from zero to two billion, VACUUM will silently limit the effective value to 95% of , so that a @@ -9403,7 +9267,7 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv; - vacuum_freeze_min_age (integer) + vacuum_freeze_min_age (integer) default is 50 million transactions vacuum_freeze_min_age configuration parameter @@ -9413,7 +9277,7 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv; Specifies the cutoff age (in transactions) that VACUUM should use to decide whether to trigger freezing of pages that have an older XID. - The default is 50 million transactions. Although + Although users can set this value anywhere from zero to one billion, VACUUM will silently limit the effective value to half the value of , so @@ -9425,7 +9289,7 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv; - vacuum_failsafe_age (integer) + vacuum_failsafe_age (integer) default is 1.6 billion transactions vacuum_failsafe_age configuration parameter @@ -9452,7 +9316,7 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv; shared buffers. - The default is 1.6 billion transactions. Although users can + Although users can set this value anywhere from zero to 2.1 billion, VACUUM will silently adjust the effective value to no less than 105% of - vacuum_multixact_freeze_table_age (integer) + vacuum_multixact_freeze_table_age (integer) default is 150 million multixacts vacuum_multixact_freeze_table_age configuration parameter @@ -9474,7 +9338,7 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv; the age specified by this setting. An aggressive scan differs from a regular VACUUM in that it visits every page that might contain unfrozen XIDs or MXIDs, not just those that might contain dead - tuples. The default is 150 million multixacts. + tuples. Although users can set this value anywhere from zero to two billion, VACUUM will silently limit the effective value to 95% of , so that a @@ -9486,7 +9350,7 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv; - vacuum_multixact_freeze_min_age (integer) + vacuum_multixact_freeze_min_age (integer) default is 5 million multixacts vacuum_multixact_freeze_min_age configuration parameter @@ -9495,7 +9359,7 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv; Specifies the cutoff age (in multixacts) that VACUUM should use to decide whether to trigger freezing of pages with - an older multixact ID. The default is 5 million multixacts. + an older multixact ID. Although users can set this value anywhere from zero to one billion, VACUUM will silently limit the effective value to half the value of , @@ -9507,7 +9371,7 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv; - vacuum_multixact_failsafe_age (integer) + vacuum_multixact_failsafe_age (integer) default is 1.6 billion multixacts vacuum_multixact_failsafe_age configuration parameter @@ -9530,7 +9394,7 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv; maintenance tasks (such as index vacuuming) are bypassed. - The default is 1.6 billion multixacts. Although users can set + Although users can set this value anywhere from zero to 2.1 billion, VACUUM will silently adjust the effective value to no less than 105% of - vacuum_max_eager_freeze_failure_rate (floating point) + vacuum_max_eager_freeze_failure_rate (floating point) default is 0.03 (3%) vacuum_max_eager_freeze_failure_rate configuration parameter @@ -9551,8 +9415,7 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv; the relation) that VACUUM may scan and fail to set all-frozen in the visibility map before disabling eager scanning. A value of 0 - disables eager scanning altogether. The default is - 0.03 (3%). + disables eager scanning altogether. @@ -9590,7 +9453,7 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv; - client_min_messages (enum) + client_min_messages (enum) default is NOTICE client_min_messages configuration parameter @@ -9605,8 +9468,7 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv; DEBUG1, LOG, NOTICE, WARNING, and ERROR. Each level includes all the levels that follow it. The later the level, - the fewer messages are sent. The default is - NOTICE. Note that LOG has a different + the fewer messages are sent. Note that LOG has a different rank here than in . @@ -9616,7 +9478,7 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv; - search_path (string) + search_path (string) default is "$user", public search_path configuration parameter @@ -9679,8 +9541,6 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv; - The default value for this parameter is - "$user", public. This setting supports shared use of a database (where no users have private schemas, and all share use of public), private per-user schemas, and combinations of these. Other @@ -9710,7 +9570,7 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv; - row_security (boolean) + row_security (boolean) default is on row_security configuration parameter @@ -9720,7 +9580,7 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv; This variable controls whether to raise an error in lieu of applying a row security policy. When set to on, policies apply normally. When set to off, queries fail which would - otherwise apply at least one policy. The default is on. + otherwise apply at least one policy. Change to off where limited row visibility could cause incorrect results; for example, pg_dump makes that change by default. This variable has no effect on roles which bypass @@ -9736,7 +9596,7 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv; - default_table_access_method (string) + default_table_access_method (string) default is heap default_table_access_method configuration parameter @@ -9747,7 +9607,7 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv; creating tables or materialized views if the CREATE command does not explicitly specify an access method, or when SELECT ... INTO is used, which does not allow - specifying a table access method. The default is heap. + specifying a table access method. @@ -9803,7 +9663,7 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv; - default_toast_compression (enum) + default_toast_compression (enum) default is pglz default_toast_compression configuration parameter @@ -9820,13 +9680,12 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv; The supported compression methods are pglz and (if PostgreSQL was compiled with ) lz4. - The default is pglz. - temp_tablespaces (string) + temp_tablespaces (string) default is '' temp_tablespaces configuration parameter @@ -9863,7 +9722,7 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv; - The default value is an empty string, which results in all temporary + If default is used, which results in all temporary objects being created in the default tablespace of the current database. @@ -9923,7 +9782,7 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv; - default_transaction_read_only (boolean) + default_transaction_read_only (boolean) default is off (read/write). read-only transaction setting default @@ -9936,9 +9795,8 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv; A read-only SQL transaction cannot alter non-temporary tables. This parameter controls the default read-only status of each new - transaction. The default is off (read/write). + transaction. - Consult for more information. @@ -9946,7 +9804,7 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv; - default_transaction_deferrable (boolean) + default_transaction_deferrable (boolean) default is off deferrable transaction setting default @@ -9970,7 +9828,7 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv; This parameter controls the default deferrable status of each new transaction. It currently has no effect on read-write transactions or those operating at isolation levels lower - than serializable. The default is off. + than serializable. @@ -9980,7 +9838,7 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv; - transaction_isolation (enum) + transaction_isolation (enum) default is default_transaction_isolation value transaction isolation level @@ -10000,7 +9858,7 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv; - transaction_read_only (boolean) + transaction_read_only (boolean) default is default_transaction_read_only value read-only transaction @@ -10020,7 +9878,7 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv; - transaction_deferrable (boolean) + transaction_deferrable (boolean) default is default_transaction_deferrable value deferrable transaction @@ -10041,7 +9899,7 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv; - session_replication_role (enum) + session_replication_role (enum) default is origin session_replication_role configuration parameter @@ -10050,7 +9908,7 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv; Controls firing of replication-related triggers and rules for the current session. - Possible values are origin (the default), + Possible values are origin, replica and local. Setting this parameter results in discarding any previously cached query plans. @@ -10085,7 +9943,7 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv; - statement_timeout (integer) + statement_timeout (integer) default is 0 statement_timeout configuration parameter @@ -10097,7 +9955,6 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv; to ERROR or lower, the statement that timed out will also be logged. If this value is specified without units, it is taken as milliseconds. - A value of zero (the default) disables the timeout. @@ -10121,7 +9978,7 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv; - transaction_timeout (integer) + transaction_timeout (integer) default is 0 transaction_timeout configuration parameter @@ -10133,7 +9990,6 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv; (started with BEGIN) and to an implicitly started transaction corresponding to a single statement. If this value is specified without units, it is taken as milliseconds. - A value of zero (the default) disables the timeout. @@ -10157,7 +10013,7 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv; - lock_timeout (integer) + lock_timeout (integer) default is 0 lock_timeout configuration parameter @@ -10172,7 +10028,6 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv; FOR UPDATE without NOWAIT) and to implicitly-acquired locks. If this value is specified without units, it is taken as milliseconds. - A value of zero (the default) disables the timeout. @@ -10194,7 +10049,7 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv; - idle_in_transaction_session_timeout (integer) + idle_in_transaction_session_timeout (integer) default is 0 idle_in_transaction_session_timeout configuration parameter @@ -10205,7 +10060,6 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv; client query) within an open transaction for longer than the specified amount of time. If this value is specified without units, it is taken as milliseconds. - A value of zero (the default) disables the timeout. @@ -10220,7 +10074,7 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv; - idle_session_timeout (integer) + idle_session_timeout (integer) default is 0 idle_session_timeout configuration parameter @@ -10231,7 +10085,6 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv; client query), but not within an open transaction, for longer than the specified amount of time. If this value is specified without units, it is taken as milliseconds. - A value of zero (the default) disables the timeout. @@ -10252,7 +10105,7 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv; - bytea_output (enum) + bytea_output (enum) default is hex bytea_output configuration parameter @@ -10260,7 +10113,7 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv; Sets the output format for values of type bytea. - Valid values are hex (the default) + Valid values are hex and escape (the traditional PostgreSQL format). See for more information. The bytea type always @@ -10270,7 +10123,7 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv; - xmlbinary (enum) + xmlbinary (enum) default is base64 xmlbinary configuration parameter @@ -10282,8 +10135,7 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv; XML by the functions xmlelement or xmlforest. Possible values are base64 and hex, which - are both defined in the XML Schema standard. The default is - base64. For further information about + are both defined in the XML Schema standard. For further information about XML-related functions, see . @@ -10298,7 +10150,7 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv; - xmloption (enum) + xmloption (enum) default is CONTENT xmloption configuration parameter @@ -10316,7 +10168,6 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv; XML and character string values. See for a description of this. Valid values are DOCUMENT and - CONTENT. The default is CONTENT. @@ -10331,7 +10182,7 @@ SET XML OPTION { DOCUMENT | CONTENT }; - gin_pending_list_limit (integer) + gin_pending_list_limit (integer) default is 4MB gin_pending_list_limit configuration parameter @@ -10344,8 +10195,7 @@ SET XML OPTION { DOCUMENT | CONTENT }; larger than this maximum size, it is cleaned up by moving the entries in it to the index's main GIN data structure in bulk. If this value is specified without units, it is taken as kilobytes. - The default is four megabytes (4MB). This setting - can be overridden for individual GIN indexes by changing + This setting can be overridden for individual GIN indexes by changing index storage parameters. See and for more information. @@ -10354,7 +10204,7 @@ SET XML OPTION { DOCUMENT | CONTENT }; - createrole_self_grant (string) + createrole_self_grant (string) default is '' createrole_self_grant configuration parameter @@ -10367,8 +10217,7 @@ SET XML OPTION { DOCUMENT | CONTENT }; is set to a non-empty value, the newly-created role will be granted to the creating user with the options specified. The value must be set, inherit, or a - comma-separated list of these. The default value is an empty string, - which disables the feature. + comma-separated list of these. if an empty string then disables the feature. The purpose of this option is to allow a CREATEROLE @@ -10388,7 +10237,7 @@ SET XML OPTION { DOCUMENT | CONTENT }; - event_triggers (boolean) + event_triggers (boolean) default is true event_triggers configuration parameter @@ -10399,15 +10248,15 @@ SET XML OPTION { DOCUMENT | CONTENT }; Allow temporarily disabling execution of event triggers in order to troubleshoot and repair faulty event triggers. All event triggers will be disabled by setting it to false. Setting the value - to true allows all event triggers to fire, this - is the default value. Only superusers and users with the appropriate + to true allows all event triggers to fire. + Only superusers and users with the appropriate SET privilege can change this setting. - restrict_nonsystem_relation_kind (string) + restrict_nonsystem_relation_kind (string) default is '' restrict_nonsystem_relation_kind configuration parameter @@ -10431,7 +10280,7 @@ SET XML OPTION { DOCUMENT | CONTENT }; - DateStyle (string) + DateStyle (string) - default is ISO, MDY DateStyle configuration parameter @@ -10450,8 +10299,8 @@ SET XML OPTION { DOCUMENT | CONTENT }; keywords US, NonEuro, and NonEuropean are synonyms for MDY. See for more information. The - built-in default is ISO, MDY, but - initdb will initialize the + built-in default can be changed by + initdb, which will initialize the configuration file with a setting that corresponds to the behavior of the chosen lc_time locale. @@ -10459,7 +10308,7 @@ SET XML OPTION { DOCUMENT | CONTENT }; - IntervalStyle (enum) + IntervalStyle (enum) - default is postgres IntervalStyle configuration parameter @@ -10469,7 +10318,7 @@ SET XML OPTION { DOCUMENT | CONTENT }; Sets the display format for interval values. The value sql_standard will produce output matching SQL standard interval literals. - The value postgres (which is the default) will produce + The value postgres will produce output matching PostgreSQL releases prior to 8.4 when the parameter was set to ISO. @@ -10490,7 +10339,7 @@ SET XML OPTION { DOCUMENT | CONTENT }; - TimeZone (string) + TimeZone (string) - default is GMT TimeZone configuration parameter @@ -10499,7 +10348,7 @@ SET XML OPTION { DOCUMENT | CONTENT }; Sets the time zone for displaying and interpreting time stamps. - The built-in default is GMT, but that is typically + The default is typically overridden in postgresql.conf; initdb will install a setting there corresponding to its system environment. See for more information. @@ -10508,7 +10357,7 @@ SET XML OPTION { DOCUMENT | CONTENT }; - timezone_abbreviations (string) + timezone_abbreviations (string) default is 'Default' timezone_abbreviations configuration parameter @@ -10519,8 +10368,7 @@ SET XML OPTION { DOCUMENT | CONTENT }; Sets the collection of additional time zone abbreviations that will be accepted by the server for datetime input (beyond any abbreviations defined by the current TimeZone - setting). The default is 'Default', - which is a collection that works in most of the world; there are + setting). The default value is a collection that works in most of the world; there are also 'Australia' and 'India', and other collections can be defined for a particular installation. See for more information. @@ -10529,7 +10377,7 @@ SET XML OPTION { DOCUMENT | CONTENT }; - extra_float_digits (integer) + extra_float_digits (integer) - default is 1 significant digits @@ -10548,7 +10396,7 @@ SET XML OPTION { DOCUMENT | CONTENT }; and geometric data types. - If the value is 1 (the default) or above, float values are output in + If the value is 1 or above, float values are output in shortest-precise format; see . The actual number of digits generated depends only on the value being output, not on the value of this parameter. At most 17 digits are @@ -10579,7 +10427,7 @@ SET XML OPTION { DOCUMENT | CONTENT }; - client_encoding (string) + client_encoding (string) - default is the database encoding. client_encoding configuration parameter @@ -10588,7 +10436,6 @@ SET XML OPTION { DOCUMENT | CONTENT }; Sets the client-side encoding (character set). - The default is to use the database encoding. The character sets supported by the PostgreSQL server are described in . @@ -10596,7 +10443,7 @@ SET XML OPTION { DOCUMENT | CONTENT }; - lc_messages (string) + lc_messages (string) - default is '' lc_messages configuration parameter @@ -10606,7 +10453,7 @@ SET XML OPTION { DOCUMENT | CONTENT }; Sets the language in which messages are displayed. Acceptable values are system-dependent; see for more information. If this variable is set to the empty string - (which is the default) then the value is inherited from the + then the value is inherited from the execution environment of the server in a system-dependent way. @@ -10626,7 +10473,7 @@ SET XML OPTION { DOCUMENT | CONTENT }; - lc_monetary (string) + lc_monetary (string) - default is '' lc_monetary configuration parameter @@ -10637,7 +10484,7 @@ SET XML OPTION { DOCUMENT | CONTENT }; example with the to_char family of functions. Acceptable values are system-dependent; see for more information. If this variable is - set to the empty string (which is the default) then the value + set to the empty string then the value is inherited from the execution environment of the server in a system-dependent way. @@ -10645,7 +10492,7 @@ SET XML OPTION { DOCUMENT | CONTENT }; - lc_numeric (string) + lc_numeric (string) - default is '' lc_numeric configuration parameter @@ -10656,7 +10503,7 @@ SET XML OPTION { DOCUMENT | CONTENT }; with the to_char family of functions. Acceptable values are system-dependent; see for more information. If this variable is - set to the empty string (which is the default) then the value + set to the empty string then the value is inherited from the execution environment of the server in a system-dependent way. @@ -10664,7 +10511,7 @@ SET XML OPTION { DOCUMENT | CONTENT }; - lc_time (string) + lc_time (string) - default is '' lc_time configuration parameter @@ -10675,7 +10522,7 @@ SET XML OPTION { DOCUMENT | CONTENT }; with the to_char family of functions. Acceptable values are system-dependent; see for more information. If this variable is - set to the empty string (which is the default) then the value + set to the empty string then the value is inherited from the execution environment of the server in a system-dependent way. @@ -10683,7 +10530,7 @@ SET XML OPTION { DOCUMENT | CONTENT }; - icu_validation_level (enum) + icu_validation_level (enum) - default is WARNING icu_validation_level configuration parameter @@ -10703,13 +10550,13 @@ SET XML OPTION { DOCUMENT | CONTENT }; If set to DISABLED, does not report validation problems at all. Otherwise reports problems at the given message - level. The default is WARNING. + level. - default_text_search_config (string) + default_text_search_config (string) - default is pg_catalog.simple default_text_search_config configuration parameter @@ -10720,8 +10567,8 @@ SET XML OPTION { DOCUMENT | CONTENT }; of the text search functions that do not have an explicit argument specifying the configuration. See for further information. - The built-in default is pg_catalog.simple, but - initdb will initialize the + The built-in default can be changed by + initdb, which will initialize the configuration file with a setting that corresponds to the chosen lc_ctype locale, if a configuration matching that locale can be identified. @@ -10771,7 +10618,7 @@ SET XML OPTION { DOCUMENT | CONTENT }; - local_preload_libraries (string) + local_preload_libraries (string) default is '' local_preload_libraries configuration parameter @@ -10825,7 +10672,7 @@ SET XML OPTION { DOCUMENT | CONTENT }; - session_preload_libraries (string) + session_preload_libraries (string) default is '' session_preload_libraries configuration parameter @@ -10868,7 +10715,7 @@ SET XML OPTION { DOCUMENT | CONTENT }; - shared_preload_libraries (string) + shared_preload_libraries (string) default is '' shared_preload_libraries configuration parameter @@ -10918,7 +10765,7 @@ SET XML OPTION { DOCUMENT | CONTENT }; - jit_provider (string) + jit_provider (string) - default is llvmjit jit_provider configuration parameter @@ -10927,7 +10774,6 @@ SET XML OPTION { DOCUMENT | CONTENT }; This variable is the name of the JIT provider library to be used (see ). - The default is llvmjit. This parameter can only be set at server start. @@ -10949,7 +10795,7 @@ SET XML OPTION { DOCUMENT | CONTENT }; - dynamic_library_path (string) + dynamic_library_path (string) default is '$libdir' dynamic_library_path configuration parameter @@ -10986,8 +10832,7 @@ dynamic_library_path = 'C:\tools\postgresql;H:\my_project\lib;$libdir' - The default value for this parameter is - '$libdir'. If the value is set to an empty + If the value is set to an empty string, the automatic path search is turned off. @@ -11004,7 +10849,7 @@ dynamic_library_path = 'C:\tools\postgresql;H:\my_project\lib;$libdir' - extension_control_path (string) + extension_control_path (string) default is '$system' extension_control_path configuration parameter @@ -11044,8 +10889,7 @@ extension_control_path = 'C:\tools\postgresql;H:\my_project\share;$system' - The default value for this parameter is - '$system'. If the value is set to an empty + If the value is set to an empty string, the default '$system' is also assumed. @@ -11073,7 +10917,7 @@ dynamic_library_path = '/usr/local/lib/postgresql:$libdir' - gin_fuzzy_search_limit (integer) + gin_fuzzy_search_limit (integer) default is 0 gin_fuzzy_search_limit configuration parameter @@ -11096,7 +10940,7 @@ dynamic_library_path = '/usr/local/lib/postgresql:$libdir' - deadlock_timeout (integer) + deadlock_timeout (integer) default is 1s deadlock timeout during @@ -11121,7 +10965,6 @@ dynamic_library_path = '/usr/local/lib/postgresql:$libdir' wasted in needless deadlock checks, but slows down reporting of real deadlock errors. If this value is specified without units, it is taken as milliseconds. - The default is one second (1s), which is probably about the smallest value you would want in practice. On a heavily loaded server you might want to raise it. Ideally the setting should exceed your typical transaction time, @@ -11142,7 +10985,7 @@ dynamic_library_path = '/usr/local/lib/postgresql:$libdir' - max_locks_per_transaction (integer) + max_locks_per_transaction (integer) default is 64 max_locks_per_transaction configuration parameter @@ -11157,8 +11000,8 @@ dynamic_library_path = '/usr/local/lib/postgresql:$libdir' locks used by each transaction; individual transactions can lock more objects as long as the locks of all transactions fit in the lock table. This is not the number of - rows that can be locked; that value is unlimited. The default, - 64, has historically proven sufficient, but you might need to + rows that can be locked; that value is unlimited. The default value + has historically proven sufficient, but you might need to raise this value if you have queries that touch many different tables in a single transaction, e.g., query of a parent table with many children. This parameter can only be set at server start. @@ -11173,7 +11016,7 @@ dynamic_library_path = '/usr/local/lib/postgresql:$libdir' - max_pred_locks_per_transaction (integer) + max_pred_locks_per_transaction (integer) default is 64 max_pred_locks_per_transaction configuration parameter @@ -11188,8 +11031,8 @@ dynamic_library_path = '/usr/local/lib/postgresql:$libdir' locks used by each transaction; individual transactions can lock more objects as long as the locks of all transactions fit in the lock table. This is not the number of - rows that can be locked; that value is unlimited. The default, - 64, has historically proven sufficient, but you might need to + rows that can be locked; that value is unlimited. The default value + has historically proven sufficient, but you might need to raise this value if you have clients that touch many different tables in a single serializable transaction. This parameter can only be set at server start. @@ -11198,7 +11041,7 @@ dynamic_library_path = '/usr/local/lib/postgresql:$libdir' - max_pred_locks_per_relation (integer) + max_pred_locks_per_relation (integer) default is -2 max_pred_locks_per_relation configuration parameter @@ -11210,7 +11053,7 @@ dynamic_library_path = '/usr/local/lib/postgresql:$libdir' relation. Values greater than or equal to zero mean an absolute limit, while negative values mean divided by - the absolute value of this setting. The default is -2, which keeps + the absolute value of this setting. Value of -2, which keeps the behavior from previous versions of PostgreSQL. This parameter can only be set in the postgresql.conf file or on the server command line. @@ -11219,7 +11062,7 @@ dynamic_library_path = '/usr/local/lib/postgresql:$libdir' - max_pred_locks_per_page (integer) + max_pred_locks_per_page (integer) default is 2 max_pred_locks_per_page configuration parameter @@ -11227,8 +11070,8 @@ dynamic_library_path = '/usr/local/lib/postgresql:$libdir' This controls how many rows on a single page can be predicate-locked - before the lock is promoted to covering the whole page. The default - is 2. This parameter can only be set in + before the lock is promoted to covering the whole page. + This parameter can only be set in the postgresql.conf file or on the server command line. @@ -11246,7 +11089,7 @@ dynamic_library_path = '/usr/local/lib/postgresql:$libdir' - array_nulls (boolean) + array_nulls (boolean) default is on array_nulls configuration parameter @@ -11255,7 +11098,7 @@ dynamic_library_path = '/usr/local/lib/postgresql:$libdir' This controls whether the array input parser recognizes unquoted NULL as specifying a null array element. - By default, this is on, allowing array values containing + Setting this value to on, allowing array values containing null values to be entered. However, PostgreSQL versions before 8.2 did not support null values in arrays, and therefore would treat NULL as specifying a normal array element with @@ -11272,7 +11115,7 @@ dynamic_library_path = '/usr/local/lib/postgresql:$libdir' - backslash_quote (enum) + backslash_quote (enum) default is safe_encoding stringsbackslash quotes backslash_quote configuration parameter @@ -11296,7 +11139,6 @@ dynamic_library_path = '/usr/local/lib/postgresql:$libdir' off (reject always), and safe_encoding (allow only if client encoding does not allow ASCII \ within a multibyte character). - safe_encoding is the default setting. @@ -11309,7 +11151,7 @@ dynamic_library_path = '/usr/local/lib/postgresql:$libdir' - escape_string_warning (boolean) + escape_string_warning (boolean) default is on stringsescape warning escape_string_warning configuration parameter @@ -11320,7 +11162,6 @@ dynamic_library_path = '/usr/local/lib/postgresql:$libdir' When on, a warning is issued if a backslash (\) appears in an ordinary string literal ('...' syntax) and standard_conforming_strings is off. - The default is on. Applications that wish to use backslash as escape should be @@ -11333,7 +11174,7 @@ dynamic_library_path = '/usr/local/lib/postgresql:$libdir' - lo_compat_privileges (boolean) + lo_compat_privileges (boolean) default is off lo_compat_privileges configuration parameter @@ -11344,8 +11185,7 @@ dynamic_library_path = '/usr/local/lib/postgresql:$libdir' did not have access privileges and were, therefore, always readable and writable by all users. Setting this variable to on disables the new privilege checks, for compatibility with prior - releases. The default is off. - Only superusers and users with the appropriate SET + releases. Only superusers and users with the appropriate SET privilege can change this setting. @@ -11357,7 +11197,7 @@ dynamic_library_path = '/usr/local/lib/postgresql:$libdir' - quote_all_identifiers (boolean) + quote_all_identifiers (boolean) default is off quote_all_identifiers configuration parameter @@ -11375,7 +11215,7 @@ dynamic_library_path = '/usr/local/lib/postgresql:$libdir' - standard_conforming_strings (boolean) + standard_conforming_strings (boolean) default is on stringsstandard conforming standard_conforming_strings configuration parameter @@ -11386,8 +11226,8 @@ dynamic_library_path = '/usr/local/lib/postgresql:$libdir' This controls whether ordinary string literals ('...') treat backslashes literally, as specified in the SQL standard. - Beginning in PostgreSQL 9.1, the default is - on (prior releases defaulted to off). + Beginning in PostgreSQL 9.1, + (prior releases defaulted to off). Applications can check this parameter to determine how string literals will be processed. The presence of this parameter can also be taken as an indication @@ -11400,7 +11240,7 @@ dynamic_library_path = '/usr/local/lib/postgresql:$libdir' - synchronize_seqscans (boolean) + synchronize_seqscans (boolean) default is on synchronize_seqscans configuration parameter @@ -11416,8 +11256,7 @@ dynamic_library_path = '/usr/local/lib/postgresql:$libdir' unpredictable changes in the row ordering returned by queries that have no ORDER BY clause. Setting this parameter to off ensures the pre-8.3 behavior in which a sequential - scan always starts from the beginning of the table. The default - is on. + scan always starts from the beginning of the table. @@ -11430,7 +11269,7 @@ dynamic_library_path = '/usr/local/lib/postgresql:$libdir' - transform_null_equals (boolean) + transform_null_equals (boolean) default is off IS NULL transform_null_equals configuration parameter @@ -11445,8 +11284,7 @@ dynamic_library_path = '/usr/local/lib/postgresql:$libdir' return true if expr evaluates to the null value, and false otherwise. The correct SQL-spec-compliant behavior of expr = NULL is to always - return null (unknown). Therefore this parameter defaults to - off. + return null (unknown). @@ -11460,7 +11298,7 @@ dynamic_library_path = '/usr/local/lib/postgresql:$libdir' very useful and do not appear often in normal applications so this option does little harm in practice. But new users are frequently confused about the semantics of expressions - involving null values, so this option is off by default. + involving null values @@ -11478,7 +11316,7 @@ dynamic_library_path = '/usr/local/lib/postgresql:$libdir' - allow_alter_system (boolean) + allow_alter_system (boolean) default is on allow_alter_system configuration parameter @@ -11489,7 +11327,7 @@ dynamic_library_path = '/usr/local/lib/postgresql:$libdir' off, an error is returned if the ALTER SYSTEM command is executed. This parameter can only be set in the postgresql.conf file or on the server command - line. The default value is on. + line. @@ -11535,29 +11373,28 @@ dynamic_library_path = '/usr/local/lib/postgresql:$libdir' - exit_on_error (boolean) + exit_on_error (boolean) default is off exit_on_error configuration parameter - If on, any error will terminate the current session. By default, - this is set to off, so that only FATAL errors will terminate the - session. + If on, any error will terminate the current session. If default is used, + then only FATAL errors will terminate the session. - restart_after_crash (boolean) + restart_after_crash (boolean) default is on restart_after_crash configuration parameter - When set to on, which is the default, PostgreSQL + If this is set to on, PostgreSQL will automatically reinitialize after a backend crash. Leaving this value set to on is normally the best way to maximize the availability of the database. However, in some circumstances, such as when @@ -11574,14 +11411,14 @@ dynamic_library_path = '/usr/local/lib/postgresql:$libdir' - data_sync_retry (boolean) + data_sync_retry (boolean) default is off data_sync_retry configuration parameter - When set to off, which is the default, PostgreSQL + If this is set to off, PostgreSQL will raise a PANIC-level error on failure to flush modified data files to the file system. This causes the database server to crash. This parameter can only be set at server start. @@ -11607,14 +11444,14 @@ dynamic_library_path = '/usr/local/lib/postgresql:$libdir' - recovery_init_sync_method (enum) + recovery_init_sync_method (enum) default is fsync recovery_init_sync_method configuration parameter - When set to fsync, which is the default, + When set to fsync, PostgreSQL will recursively open and synchronize all files in the data directory before crash recovery begins. The search for files will follow symbolic links for the WAL @@ -11666,7 +11503,7 @@ dynamic_library_path = '/usr/local/lib/postgresql:$libdir' - block_size (integer) + block_size (integer) default is 8192 block_size configuration parameter @@ -11674,8 +11511,8 @@ dynamic_library_path = '/usr/local/lib/postgresql:$libdir' Reports the size of a disk block. It is determined by the value - of BLCKSZ when building the server. The default - value is 8192 bytes. The meaning of some configuration + of BLCKSZ when building the server. + The meaning of some configuration variables (such as ) is influenced by block_size. See for information. @@ -11684,7 +11521,7 @@ dynamic_library_path = '/usr/local/lib/postgresql:$libdir' - data_checksums (boolean) + data_checksums (boolean) default is off data_checksums configuration parameter @@ -11698,7 +11535,7 @@ dynamic_library_path = '/usr/local/lib/postgresql:$libdir' - data_directory_mode (integer) + data_directory_mode (integer) default is 0700 data_directory_mode configuration parameter @@ -11718,7 +11555,7 @@ dynamic_library_path = '/usr/local/lib/postgresql:$libdir' - debug_assertions (boolean) + debug_assertions (boolean) default is without assertions. debug_assertions configuration parameter @@ -11730,15 +11567,13 @@ dynamic_library_path = '/usr/local/lib/postgresql:$libdir' macro USE_ASSERT_CHECKING is defined when PostgreSQL is built (accomplished e.g., by the configure option - ). By - default PostgreSQL is built without - assertions. + ). - huge_pages_status (enum) + huge_pages_status (enum) default is off huge_pages_status configuration parameter @@ -11757,7 +11592,7 @@ dynamic_library_path = '/usr/local/lib/postgresql:$libdir' - integer_datetimes (boolean) + integer_datetimes (boolean) value is on and cannot be changed by command integer_datetimes configuration parameter @@ -11772,7 +11607,7 @@ dynamic_library_path = '/usr/local/lib/postgresql:$libdir' - in_hot_standby (boolean) + in_hot_standby (boolean) value cannot be changed by command in_hot_standby configuration parameter @@ -11789,7 +11624,7 @@ dynamic_library_path = '/usr/local/lib/postgresql:$libdir' - max_function_args (integer) + max_function_args (integer) value is 100 and cannot be changed by command max_function_args configuration parameter @@ -11797,14 +11632,13 @@ dynamic_library_path = '/usr/local/lib/postgresql:$libdir' Reports the maximum number of function arguments. It is determined by - the value of FUNC_MAX_ARGS when building the server. The - default value is 100 arguments. + the value of FUNC_MAX_ARGS when building the server. - max_identifier_length (integer) + max_identifier_length (integer) default is 63 max_identifier_length configuration parameter @@ -11814,15 +11648,13 @@ dynamic_library_path = '/usr/local/lib/postgresql:$libdir' Reports the maximum identifier length. It is determined as one less than the value of NAMEDATALEN when building the server. The default value of NAMEDATALEN is - 64; therefore the default - max_identifier_length is 63 bytes, which - can be less than 63 characters when using multibyte encodings. + 64. Its value can be less than 63 characters when using multibyte encodings. - max_index_keys (integer) + max_index_keys (integer) default is 32 keys max_index_keys configuration parameter @@ -11830,8 +11662,7 @@ dynamic_library_path = '/usr/local/lib/postgresql:$libdir' Reports the maximum number of index keys. It is determined by - the value of INDEX_MAX_KEYS when building the server. The - default value is 32 keys. + the value of INDEX_MAX_KEYS when building the server. @@ -11855,7 +11686,7 @@ dynamic_library_path = '/usr/local/lib/postgresql:$libdir' - segment_size (integer) + segment_size (integer) default is 1GB segment_size configuration parameter @@ -11866,13 +11697,13 @@ dynamic_library_path = '/usr/local/lib/postgresql:$libdir' segment. It is determined by the value of RELSEG_SIZE when building the server. The maximum size of a segment file in bytes is equal to segment_size multiplied by - block_size; by default this is 1GB. + block_size. - server_encoding (string) + server_encoding (string) no default value, its defined on database creation. server_encoding configuration parameter @@ -11889,7 +11720,7 @@ dynamic_library_path = '/usr/local/lib/postgresql:$libdir' - server_version (string) + server_version (string) no default value server_version configuration parameter @@ -11903,7 +11734,7 @@ dynamic_library_path = '/usr/local/lib/postgresql:$libdir' - server_version_num (integer) + server_version_num (integer) no default value and cannot be changed by command server_version_num configuration parameter @@ -11917,7 +11748,7 @@ dynamic_library_path = '/usr/local/lib/postgresql:$libdir' - shared_memory_size (integer) + shared_memory_size (integer) cannot be changed by command shared_memory_size configuration parameter @@ -11931,7 +11762,7 @@ dynamic_library_path = '/usr/local/lib/postgresql:$libdir' - shared_memory_size_in_huge_pages (integer) + shared_memory_size_in_huge_pages (integer) default is -1 and cannot be changed by command shared_memory_size_in_huge_pages configuration parameter @@ -11952,7 +11783,7 @@ dynamic_library_path = '/usr/local/lib/postgresql:$libdir' - ssl_library (string) + ssl_library (string) cannot be changed by command, depends on library server was built ssl_library configuration parameter @@ -11968,7 +11799,7 @@ dynamic_library_path = '/usr/local/lib/postgresql:$libdir' - wal_block_size (integer) + wal_block_size (integer) default is 8Kbytes and cannot be changed by command wal_block_size configuration parameter @@ -11976,22 +11807,20 @@ dynamic_library_path = '/usr/local/lib/postgresql:$libdir' Reports the size of a WAL disk block. It is determined by the value - of XLOG_BLCKSZ when building the server. The default value - is 8192 bytes. + of XLOG_BLCKSZ when building the server. - wal_segment_size (integer) + wal_segment_size (integer) default is 16MB and cannot be changed by command wal_segment_size configuration parameter - Reports the size of write ahead log segments. The default value is - 16MB. See for more information. + Reports the size of write ahead log segments. See for more information. @@ -12042,7 +11871,7 @@ dynamic_library_path = '/usr/local/lib/postgresql:$libdir' - allow_in_place_tablespaces (boolean) + allow_in_place_tablespaces (boolean) default is off allow_in_place_tablespaces configuration parameter @@ -12063,7 +11892,7 @@ dynamic_library_path = '/usr/local/lib/postgresql:$libdir' - allow_system_table_mods (boolean) + allow_system_table_mods (boolean) default is off allow_system_table_mods configuration parameter @@ -12082,7 +11911,7 @@ dynamic_library_path = '/usr/local/lib/postgresql:$libdir' - backtrace_functions (string) + backtrace_functions (string) default is '' backtrace_functions configuration parameter @@ -12109,7 +11938,7 @@ dynamic_library_path = '/usr/local/lib/postgresql:$libdir' - debug_copy_parse_plan_trees (boolean) + debug_copy_parse_plan_trees (boolean) default is off debug_copy_parse_plan_trees configuration parameter @@ -12118,7 +11947,7 @@ dynamic_library_path = '/usr/local/lib/postgresql:$libdir' Enabling this forces all parse and plan trees to be passed through copyObject(), to facilitate catching errors and - omissions in copyObject(). The default is off. + omissions in copyObject(). @@ -12132,7 +11961,7 @@ dynamic_library_path = '/usr/local/lib/postgresql:$libdir' - debug_discard_caches (integer) + debug_discard_caches (integer) default is 0 debug_discard_caches configuration parameter @@ -12145,8 +11974,7 @@ dynamic_library_path = '/usr/local/lib/postgresql:$libdir' system catalogs is effectively disabled as a result, so the server will run extremely slowly. Higher values run the cache invalidation recursively, which is even slower and only useful for testing - the caching logic itself. The default value of 0 - selects normal catalog caching behavior. + the caching logic itself. Value of 0 selects normal catalog caching behavior. @@ -12170,7 +11998,7 @@ dynamic_library_path = '/usr/local/lib/postgresql:$libdir' - debug_io_direct (string) + debug_io_direct (string) default is '' debug_io_direct configuration parameter @@ -12183,7 +12011,7 @@ dynamic_library_path = '/usr/local/lib/postgresql:$libdir' FILE_FLAG_NO_BUFFERING (Windows). - May be set to an empty string (the default) to disable use of direct + A value of '' is used to to disable use of direct I/O, or a comma-separated list of operations that should use direct I/O. The valid options are data for main data files, wal for WAL files, and @@ -12202,7 +12030,7 @@ dynamic_library_path = '/usr/local/lib/postgresql:$libdir' - debug_parallel_query (enum) + debug_parallel_query (enum) default is off debug_parallel_query configuration parameter @@ -12247,7 +12075,7 @@ dynamic_library_path = '/usr/local/lib/postgresql:$libdir' - debug_raw_expression_coverage_test (boolean) + debug_raw_expression_coverage_test (boolean) default is off debug_raw_expression_coverage_test configuration parameter @@ -12256,8 +12084,7 @@ dynamic_library_path = '/usr/local/lib/postgresql:$libdir' Enabling this forces all raw parse trees for DML statements to be scanned by raw_expression_tree_walker(), to - facilitate catching errors and omissions in that function. The - default is off. + facilitate catching errors and omissions in that function. @@ -12271,7 +12098,7 @@ dynamic_library_path = '/usr/local/lib/postgresql:$libdir' - debug_write_read_parse_plan_trees (boolean) + debug_write_read_parse_plan_trees (boolean) default is off debug_write_read_parse_plan_trees configuration parameter @@ -12280,8 +12107,7 @@ dynamic_library_path = '/usr/local/lib/postgresql:$libdir' Enabling this forces all parse and plan trees to be passed through outfuncs.c/readfuncs.c, to - facilitate catching errors and omissions in those modules. The - default is off. + facilitate catching errors and omissions in those modules. @@ -12295,7 +12121,7 @@ dynamic_library_path = '/usr/local/lib/postgresql:$libdir' - ignore_system_indexes (boolean) + ignore_system_indexes (boolean) default is off ignore_system_indexes configuration parameter @@ -12311,7 +12137,7 @@ dynamic_library_path = '/usr/local/lib/postgresql:$libdir' - post_auth_delay (integer) + post_auth_delay (integer) default is 0 post_auth_delay configuration parameter @@ -12323,14 +12149,13 @@ dynamic_library_path = '/usr/local/lib/postgresql:$libdir' authentication procedure. This is intended to give developers an opportunity to attach to the server process with a debugger. If this value is specified without units, it is taken as seconds. - A value of zero (the default) disables the delay. This parameter cannot be changed after session start. - pre_auth_delay (integer) + pre_auth_delay (integer) default is 0 pre_auth_delay configuration parameter @@ -12343,7 +12168,6 @@ dynamic_library_path = '/usr/local/lib/postgresql:$libdir' opportunity to attach to the server process with a debugger to trace down misbehavior in authentication. If this value is specified without units, it is taken as seconds. - A value of zero (the default) disables the delay. This parameter can only be set in the postgresql.conf file or on the server command line. @@ -12351,7 +12175,7 @@ dynamic_library_path = '/usr/local/lib/postgresql:$libdir' - trace_notify (boolean) + trace_notify (boolean) default is off, but exists only if LOCK_DEBUG was used trace_notify configuration parameter @@ -12369,7 +12193,7 @@ dynamic_library_path = '/usr/local/lib/postgresql:$libdir' - trace_sort (boolean) + trace_sort (boolean) default is off, but exists only if LOCK_DEBUG was used trace_sort configuration parameter @@ -12382,7 +12206,7 @@ dynamic_library_path = '/usr/local/lib/postgresql:$libdir' - trace_locks (boolean) + trace_locks (boolean) default is off, but exists only if LOCK_DEBUG was used trace_locks configuration parameter @@ -12423,7 +12247,7 @@ LOG: CleanUpLock: deleting: lock(0xb7acd844) id(24688,24696,0,0,0,1) - trace_lwlocks (boolean) + trace_lwlocks (boolean) default is off, but exists only if LOCK_DEBUG was used trace_lwlocks configuration parameter @@ -12443,7 +12267,7 @@ LOG: CleanUpLock: deleting: lock(0xb7acd844) id(24688,24696,0,0,0,1) - trace_userlocks (boolean) + trace_userlocks (boolean) default is off, but exists only if LOCK_DEBUG was used trace_userlocks configuration parameter @@ -12462,7 +12286,7 @@ LOG: CleanUpLock: deleting: lock(0xb7acd844) id(24688,24696,0,0,0,1) - trace_lock_oidmin (integer) + trace_lock_oidmin (integer) default is off, but exists only if LOCK_DEBUG was used trace_lock_oidmin configuration parameter @@ -12481,7 +12305,7 @@ LOG: CleanUpLock: deleting: lock(0xb7acd844) id(24688,24696,0,0,0,1) - trace_lock_table (integer) + trace_lock_table (integer) default is 0, but exists only if LOCK_DEBUG was used trace_lock_table configuration parameter @@ -12499,7 +12323,7 @@ LOG: CleanUpLock: deleting: lock(0xb7acd844) id(24688,24696,0,0,0,1) - debug_deadlocks (boolean) + debug_deadlocks (boolean) default is off, but exists only if LOCK_DEBUG was used debug_deadlocks configuration parameter @@ -12518,7 +12342,7 @@ LOG: CleanUpLock: deleting: lock(0xb7acd844) id(24688,24696,0,0,0,1) - log_btree_build_stats (boolean) + log_btree_build_stats (boolean) default is off, but exists only if BTREE_BUILD_STATS was used log_btree_build_stats configuration parameter @@ -12537,7 +12361,7 @@ LOG: CleanUpLock: deleting: lock(0xb7acd844) id(24688,24696,0,0,0,1) - wal_consistency_checking (string) + wal_consistency_checking (string) default is '' wal_consistency_checking configuration parameter @@ -12555,8 +12379,7 @@ LOG: CleanUpLock: deleting: lock(0xb7acd844) id(24688,24696,0,0,0,1) - The default value of this setting is the empty string, which disables - the feature. It can be set to all to check all + It can be set to all to check all records, or to a comma-separated list of resource managers to check only records originating from those resource managers. Currently, the supported resource managers are heap, @@ -12570,7 +12393,7 @@ LOG: CleanUpLock: deleting: lock(0xb7acd844) id(24688,24696,0,0,0,1) - wal_debug (boolean) + wal_debug (boolean) default is off, but exists only if WAL_DEBUG was used wal_debug configuration parameter @@ -12586,7 +12409,7 @@ LOG: CleanUpLock: deleting: lock(0xb7acd844) id(24688,24696,0,0,0,1) - ignore_checksum_failure (boolean) + ignore_checksum_failure (boolean) default is off ignore_checksum_failure configuration parameter @@ -12604,8 +12427,7 @@ LOG: CleanUpLock: deleting: lock(0xb7acd844) id(24688,24696,0,0,0,1) or hide corruption, or other serious problems. However, it may allow you to get past the error and retrieve undamaged tuples that might still be present in the table if the block header is still sane. If the header is - corrupt an error will be reported even if this option is enabled. The - default setting is off. + corrupt an error will be reported even if this option is enabled. Only superusers and users with the appropriate SET privilege can change this setting. @@ -12613,7 +12435,7 @@ LOG: CleanUpLock: deleting: lock(0xb7acd844) id(24688,24696,0,0,0,1) - zero_damaged_pages (boolean) + zero_damaged_pages (boolean) default is off zero_damaged_pages configuration parameter @@ -12632,8 +12454,7 @@ LOG: CleanUpLock: deleting: lock(0xb7acd844) id(24688,24696,0,0,0,1) generally not set this on until you have given up hope of recovering data from the damaged pages of a table. Zeroed-out pages are not forced to disk so it is recommended to recreate the table or - the index before turning this parameter off again. The - default setting is off. + the index before turning this parameter off again. Only superusers and users with the appropriate SET privilege can change this setting. @@ -12641,14 +12462,14 @@ LOG: CleanUpLock: deleting: lock(0xb7acd844) id(24688,24696,0,0,0,1) - ignore_invalid_pages (boolean) + ignore_invalid_pages (boolean) default is off ignore_invalid_pages configuration parameter - If set to off (the default), detection of + If set to off, detection of WAL records having references to invalid pages during recovery causes PostgreSQL to raise a PANIC-level error, aborting the recovery. Setting @@ -12666,7 +12487,7 @@ LOG: CleanUpLock: deleting: lock(0xb7acd844) id(24688,24696,0,0,0,1) - jit_debugging_support (boolean) + jit_debugging_support (boolean) default is off jit_debugging_support configuration parameter @@ -12675,14 +12496,13 @@ LOG: CleanUpLock: deleting: lock(0xb7acd844) id(24688,24696,0,0,0,1) If LLVM has the required functionality, register generated functions with GDB. This makes debugging easier. - The default setting is off. This parameter can only be set at server start. - jit_dump_bitcode (boolean) + jit_dump_bitcode (boolean) default is off jit_dump_bitcode configuration parameter @@ -12692,7 +12512,6 @@ LOG: CleanUpLock: deleting: lock(0xb7acd844) id(24688,24696,0,0,0,1) Writes the generated LLVM IR out to the file system, inside . This is only useful for working on the internals of the JIT implementation. - The default setting is off. Only superusers and users with the appropriate SET privilege can change this setting. @@ -12700,7 +12519,7 @@ LOG: CleanUpLock: deleting: lock(0xb7acd844) id(24688,24696,0,0,0,1) - jit_expressions (boolean) + jit_expressions (boolean) default is on jit_expressions configuration parameter @@ -12708,14 +12527,13 @@ LOG: CleanUpLock: deleting: lock(0xb7acd844) id(24688,24696,0,0,0,1) Determines whether expressions are JIT compiled, when JIT compilation - is activated (see ). The default is - on. + is activated (see ). - jit_profiling_support (boolean) + jit_profiling_support (boolean) default is off jit_profiling_support configuration parameter @@ -12726,14 +12544,13 @@ LOG: CleanUpLock: deleting: lock(0xb7acd844) id(24688,24696,0,0,0,1) perf to profile functions generated by JIT. This writes out files to ~/.debug/jit/; the user is responsible for performing cleanup when desired. - The default setting is off. This parameter can only be set at server start. - jit_tuple_deforming (boolean) + jit_tuple_deforming (boolean) default is on jit_tuple_deforming configuration parameter @@ -12742,20 +12559,19 @@ LOG: CleanUpLock: deleting: lock(0xb7acd844) id(24688,24696,0,0,0,1) Determines whether tuple deforming is JIT compiled, when JIT compilation is activated (see ). - The default is on. - remove_temp_files_after_crash (boolean) + remove_temp_files_after_crash (boolean) default is on remove_temp_files_after_crash configuration parameter - When set to on, which is the default, + When set to on, PostgreSQL will automatically remove temporary files after a backend crash. If disabled, the files will be retained and may be used for debugging, for example. Repeated crashes @@ -12767,7 +12583,7 @@ LOG: CleanUpLock: deleting: lock(0xb7acd844) id(24688,24696,0,0,0,1) - send_abort_for_crash (boolean) + send_abort_for_crash (boolean) default is off send_abort_for_crash configuration parameter @@ -12795,7 +12611,7 @@ LOG: CleanUpLock: deleting: lock(0xb7acd844) id(24688,24696,0,0,0,1) - send_abort_for_kill (boolean) + send_abort_for_kill (boolean) default is off send_abort_for_kill configuration parameter @@ -12823,15 +12639,14 @@ LOG: CleanUpLock: deleting: lock(0xb7acd844) id(24688,24696,0,0,0,1) - debug_logical_replication_streaming (enum) + debug_logical_replication_streaming (enum) default is buffered debug_logical_replication_streaming configuration parameter - The allowed values are buffered and - immediate. The default is buffered. + The allowed values are buffered and immediate. This parameter is intended to be used to test logical decoding and replication of large transactions. The effect of debug_logical_replication_streaming is different for the -- 2.42.0.windows.2