Move log_autovacuum_min_duration into its correct sections
This GUC has already been classified as LOGGING_WHAT, but its location in postgresql.conf.sample and the documentation did not reflect that, so fix those inconsistencies. Author: Justin Pryzby Discussion: https://postgr.es/m/20210404012546.GK6592@telsasoft.com
This commit is contained in:
parent
15c1a9d9cb
commit
b094063cd1
@ -6812,6 +6812,34 @@ local0.* /var/log/postgresql
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry id="guc-log-autovacuum-min-duration" xreflabel="log_autovacuum_min_duration">
|
||||
<term><varname>log_autovacuum_min_duration</varname> (<type>integer</type>)
|
||||
<indexterm>
|
||||
<primary><varname>log_autovacuum_min_duration</varname></primary>
|
||||
<secondary>configuration parameter</secondary>
|
||||
</indexterm>
|
||||
</term>
|
||||
<listitem>
|
||||
<para>
|
||||
Causes each action executed by autovacuum to be logged if it ran for at
|
||||
least the specified amount of time. Setting this to zero logs
|
||||
all autovacuum actions. <literal>-1</literal> (the default) disables
|
||||
logging autovacuum actions.
|
||||
If this value is specified without units, it is taken as milliseconds.
|
||||
For example, if you set this to
|
||||
<literal>250ms</literal> then all automatic vacuums and analyzes that run
|
||||
250ms or longer will be logged. In addition, when this parameter is
|
||||
set to any value other than <literal>-1</literal>, a message will be
|
||||
logged if an autovacuum action is skipped due to a conflicting lock or a
|
||||
concurrently dropped relation. Enabling this parameter can be helpful
|
||||
in tracking autovacuum activity. This parameter can only be set in
|
||||
the <filename>postgresql.conf</filename> file or on the server command line;
|
||||
but the setting can be overridden for individual tables by
|
||||
changing table storage parameters.
|
||||
</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry id="guc-log-checkpoints" xreflabel="log_checkpoints">
|
||||
<term><varname>log_checkpoints</varname> (<type>boolean</type>)
|
||||
<indexterm>
|
||||
@ -7827,34 +7855,6 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv;
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry id="guc-log-autovacuum-min-duration" xreflabel="log_autovacuum_min_duration">
|
||||
<term><varname>log_autovacuum_min_duration</varname> (<type>integer</type>)
|
||||
<indexterm>
|
||||
<primary><varname>log_autovacuum_min_duration</varname></primary>
|
||||
<secondary>configuration parameter</secondary>
|
||||
</indexterm>
|
||||
</term>
|
||||
<listitem>
|
||||
<para>
|
||||
Causes each action executed by autovacuum to be logged if it ran for at
|
||||
least the specified amount of time. Setting this to zero logs
|
||||
all autovacuum actions. <literal>-1</literal> (the default) disables
|
||||
logging autovacuum actions.
|
||||
If this value is specified without units, it is taken as milliseconds.
|
||||
For example, if you set this to
|
||||
<literal>250ms</literal> then all automatic vacuums and analyzes that run
|
||||
250ms or longer will be logged. In addition, when this parameter is
|
||||
set to any value other than <literal>-1</literal>, a message will be
|
||||
logged if an autovacuum action is skipped due to a conflicting lock or a
|
||||
concurrently dropped relation. Enabling this parameter can be helpful
|
||||
in tracking autovacuum activity. This parameter can only be set in
|
||||
the <filename>postgresql.conf</filename> file or on the server command line;
|
||||
but the setting can be overridden for individual tables by
|
||||
changing table storage parameters.
|
||||
</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry id="guc-autovacuum-max-workers" xreflabel="autovacuum_max_workers">
|
||||
<term><varname>autovacuum_max_workers</varname> (<type>integer</type>)
|
||||
<indexterm>
|
||||
|
@ -531,6 +531,11 @@
|
||||
#debug_print_rewritten = off
|
||||
#debug_print_plan = off
|
||||
#debug_pretty_print = on
|
||||
#log_autovacuum_min_duration = -1 # log autovacuum activity;
|
||||
# -1 disables, 0 logs all actions and
|
||||
# their durations, > 0 logs only
|
||||
# actions running at least this number
|
||||
# of milliseconds.
|
||||
#log_checkpoints = off
|
||||
#log_connections = off
|
||||
#log_disconnections = off
|
||||
@ -616,10 +621,6 @@
|
||||
|
||||
#autovacuum = on # Enable autovacuum subprocess? 'on'
|
||||
# requires track_counts to also be on.
|
||||
#log_autovacuum_min_duration = -1 # -1 disables, 0 logs all actions and
|
||||
# their durations, > 0 logs only
|
||||
# actions running at least this number
|
||||
# of milliseconds.
|
||||
#autovacuum_max_workers = 3 # max number of autovacuum subprocesses
|
||||
# (change requires restart)
|
||||
#autovacuum_naptime = 1min # time between autovacuum runs
|
||||
|
Loading…
x
Reference in New Issue
Block a user