diff options
Diffstat (limited to 'doc/src/sgml/config.sgml')
| -rw-r--r-- | doc/src/sgml/config.sgml | 41 |
1 files changed, 23 insertions, 18 deletions
diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml index aa8f47a1591..59a0874528a 100644 --- a/doc/src/sgml/config.sgml +++ b/doc/src/sgml/config.sgml @@ -140,7 +140,7 @@ An example of what this file might look like is: <programlisting> # This is a comment -log_connections = yes +log_connections = all log_destination = 'syslog' search_path = '"$user", public' shared_buffers = 128MB @@ -337,7 +337,7 @@ UPDATE pg_settings SET setting = reset_val WHERE name = 'configuration_parameter <option>-c name=value</option> command-line parameter, or its equivalent <option>--name=value</option> variation. For example, <programlisting> -postgres -c log_connections=yes --log-destination='syslog' +postgres -c log_connections=all --log-destination='syslog' </programlisting> Settings provided in this way override those set via <filename>postgresql.conf</filename> or <command>ALTER SYSTEM</command>, @@ -2363,7 +2363,7 @@ include_dir 'conf.d' </listitem> </varlistentry> - <varlistentry id="guc_file_copy_method" xreflabel="file_copy_method"> + <varlistentry id="guc-file-copy-method" xreflabel="file_copy_method"> <term><varname>file_copy_method</varname> (<type>enum</type>) <indexterm> <primary><varname>file_copy_method</varname> configuration parameter</primary> @@ -2779,6 +2779,7 @@ include_dir 'conf.d' </para> </listitem> </itemizedlist> + The default is <literal>worker</literal>. </para> <para> This parameter can only be set at server start. @@ -2787,7 +2788,7 @@ include_dir 'conf.d' </varlistentry> <varlistentry id="guc-io-workers" xreflabel="io_workers"> - <term><varname>io_workers</varname> (<type>int</type>) + <term><varname>io_workers</varname> (<type>integer</type>) <indexterm> <primary><varname>io_workers</varname> configuration parameter</primary> </indexterm> @@ -2893,7 +2894,8 @@ include_dir 'conf.d' Sets the maximum number of parallel workers that can be started by a single utility command. Currently, the parallel utility commands that support the use of parallel workers are - <command>CREATE INDEX</command> when building a B-tree or BRIN index, + <command>CREATE INDEX</command> when building a B-tree, + GIN, or BRIN index, and <command>VACUUM</command> without <literal>FULL</literal> option. Parallel workers are taken from the pool of processes established by <xref linkend="guc-max-worker-processes"/>, limited @@ -5764,7 +5766,7 @@ ANY <replaceable class="parameter">num_sync</replaceable> ( <replaceable class=" </listitem> </varlistentry> - <varlistentry id="guc-enable_self_join_elimination" xreflabel="enable_self_join_elimination"> + <varlistentry id="guc-enable-self-join-elimination" xreflabel="enable_self_join_elimination"> <term><varname>enable_self_join_elimination</varname> (<type>boolean</type>) <indexterm> <primary><varname>enable_self_join_elimination</varname> configuration parameter</primary> @@ -7527,12 +7529,12 @@ local0.* /var/log/postgresql <entry><literal>setup_durations</literal></entry> <entry> Logs the time spent establishing the connection and setting up the - backend at the time the connection is ready to execute its first - query. The log message includes the total setup duration, starting - from the postmaster accepting the incoming connection and ending - when the connection is ready for query. It also includes the time - it took to fork the new backend and the time it took to - authenticate the user. + backend until the connection is ready to execute its first + query. The log message includes three durations: the total + setup duration (starting from the postmaster accepting the + incoming connection and ending when the connection is ready + for query), the time it took to fork the new backend, and + the time it took to authenticate the user. </entry> </row> @@ -7923,10 +7925,10 @@ log_line_prefix = '%m [%p] %q%u@%d/%a ' </listitem> </varlistentry> - <varlistentry id="guc-log-lock-failure" xreflabel="log_lock_failure"> - <term><varname>log_lock_failure</varname> (<type>boolean</type>) + <varlistentry id="guc-log-lock-failures" xreflabel="log_lock_failures"> + <term><varname>log_lock_failures</varname> (<type>boolean</type>) <indexterm> - <primary><varname>log_lock_failure</varname> configuration parameter</primary> + <primary><varname>log_lock_failures</varname> configuration parameter</primary> </indexterm> </term> <listitem> @@ -8600,7 +8602,8 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv; timing information is displayed in <link linkend="vacuum-progress-reporting"><structname>pg_stat_progress_vacuum</structname></link>, <link linkend="analyze-progress-reporting"><structname>pg_stat_progress_analyze</structname></link>, - in the output of <xref linkend="sql-vacuum"/> when the + in the output of <xref linkend="sql-vacuum"/> and + <xref linkend="sql-analyze"/> when the <literal>VERBOSE</literal> option is used, and by autovacuum for auto-vacuums and auto-analyzes when <xref linkend="guc-log-autovacuum-min-duration"/> is set. @@ -9338,7 +9341,8 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv; <varlistentry id="guc-vacuum-truncate" xreflabel="vacuum_truncate"> <term><varname>vacuum_truncate</varname> (<type>boolean</type>) <indexterm> - <primary><varname>vacuum_truncate</varname> configuration parameter</primary> + <primary><varname>vacuum_truncate</varname></primary> + <secondary>configuration parameter</secondary> </indexterm> </term> <listitem> @@ -9542,7 +9546,8 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv; <varlistentry id="guc-vacuum-max-eager-freeze-failure-rate" xreflabel="vacuum_max_eager_freeze_failure_rate"> <term><varname>vacuum_max_eager_freeze_failure_rate</varname> (<type>floating point</type>) <indexterm> - <primary><varname>vacuum_max_eager_freeze_failure_rate</varname> configuration parameter</primary> + <primary><varname>vacuum_max_eager_freeze_failure_rate</varname></primary> + <secondary>configuration parameter</secondary> </indexterm> </term> <listitem> |