</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>

</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>

#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

#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