Skip to content

Commit e543906

Browse files
committed
Document default and changeability of log_startup_progress_interval
Review for 9ce346e. Author: Álvaro Herrera <alvherre@alvh.no-ip.org> Reviewed-by: Robert Haas <robertmhaas@gmail.com> Discussion: https://postgr.es/m/202110292123.bnf6axcp27vx@alvherre.pgsql
1 parent 23a1c65 commit e543906

File tree

1 file changed

+9
-3
lines changed

1 file changed

+9
-3
lines changed

doc/src/sgml/config.sgml

+9-3
Original file line numberDiff line numberDiff line change
@@ -6562,15 +6562,21 @@ local0.* /var/log/postgresql
65626562
Sets the amount of time after which the startup process will log
65636563
a message about a long-running operation that is still in progress,
65646564
as well as the interval between further progress messages for that
6565-
operation. This setting is applied separately to each operation.
6565+
operation. The default is 10 seconds. A setting of <literal>0</literal>
6566+
disables the feature. If this value is specified without units,
6567+
it is taken as milliseconds. This setting is applied separately to
6568+
each operation.
6569+
This parameter can only be set in the <filename>postgresql.conf</filename>
6570+
file or on the server command line.
6571+
</para>
6572+
6573+
<para>
65666574
For example, if syncing the data directory takes 25 seconds and
65676575
thereafter resetting unlogged relations takes 8 seconds, and if this
65686576
setting has the default value of 10 seconds, then a messages will be
65696577
logged for syncing the data directory after it has been in progress
65706578
for 10 seconds and again after it has been in progress for 20 seconds,
65716579
but nothing will be logged for resetting unlogged operations.
6572-
A setting of <literal>0</literal> disables the feature. If this value
6573-
is specified without units, it is taken as milliseconds.
65746580
</para>
65756581
</listitem>
65766582
</varlistentry>

0 commit comments

Comments
 (0)