From: Justin Pryzby <pryzbyj@telsasoft.com>
Subject: [PATCH 2/4] log_autovacuum_min_duration is LOGGING_WHAT
Date: Sat, 3 Apr 2021 19:10:01 -0500
Not AUTOVACUUM, since 48f7e6439 and ef23a7744
---
doc/src/sgml/config.sgml | 56 +++++++++----------
src/backend/utils/misc/postgresql.conf.sample | 8 +--
2 files changed, 32 insertions(+), 32 deletions(-)
diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgmlindex 9d87b5097a..c4d5126c2a 100644--- a/doc/src/sgml/config.sgml+++ b/doc/src/sgml/config.sgml@@ -6688,6 +6688,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>
@@ -7662,34 +7690,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>
diff --git a/src/backend/utils/misc/postgresql.conf.sample b/src/backend/utils/misc/postgresql.conf.sampleindex 30cfddac1f..52c4373a79 100644--- a/src/backend/utils/misc/postgresql.conf.sample+++ b/src/backend/utils/misc/postgresql.conf.sample@@ -568,6 +568,10 @@
#log_temp_files = -1 # log temporary files equal or larger
# than the specified size in kilobytes;
# -1 disables, 0 logs all temp files
+#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.
#log_timezone = 'GMT'
#------------------------------------------------------------------------------
@@ -608,10 +612,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
--
2.17.0
--GyRA7555PLgSTuth
Content-Type: text/x-diff; charset=us-ascii
Content-Disposition: attachment;
filename="0003-track_commit_timestamp-is-REPLICATION_SENDING.patch"
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: pryzbyj@telsasoft.com
Subject: Re: [PATCH 2/4] log_autovacuum_min_duration is LOGGING_WHAT
In-Reply-To: <no-message-id-3361@localhost>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox