postgres.git / summary / log / commit / refs

commit    e543906e217509ad95c1e341de4e874f027f871b
Author:   Alvaro Herrera <alvherre@alvh.no-ip.org>
Date:     Fri Nov 05 14:31:57 2021 +0000
First released in: 15.0

    Document default and changeability of log_startup_progress_interval
    
    Review for 9ce346eabf35.
    
    Author: Álvaro Herrera <alvherre@alvh.no-ip.org>
    Reviewed-by: Robert Haas <robertmhaas@gmail.com>
    Discussion: https://postgr.es/m/202110292123.bnf6axcp27vx@alvherre.pgsql


doc/src/sgml/config.sgml | 12 +++++++++--- 1 file changed, 9 insertions(+), 3 deletions(-) diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml index de77f145736..3f806740d5d 100644 --- a/doc/src/sgml/config.sgml +++ b/doc/src/sgml/config.sgml @@ -6562,15 +6562,21 @@ local0.* /var/log/postgresql Sets the amount of time after which the startup process will log a message about a long-running operation that is still in progress, as well as the interval between further progress messages for that - operation. This setting is applied separately to each operation. + operation. The default is 10 seconds. A setting of <literal>0</literal> + disables the feature. If this value is specified without units, + it is taken as milliseconds. This setting is applied separately to + each operation. + This parameter can only be set in the <filename>postgresql.conf</filename> + file or on the server command line. + </para> + + <para> For example, if syncing the data directory takes 25 seconds and thereafter resetting unlogged relations takes 8 seconds, and if this setting has the default value of 10 seconds, then a messages will be logged for syncing the data directory after it has been in progress for 10 seconds and again after it has been in progress for 20 seconds, but nothing will be logged for resetting unlogged operations. - A setting of <literal>0</literal> disables the feature. If this value - is specified without units, it is taken as milliseconds. </para> </listitem> </varlistentry> [parent: 23a1c6578c87]