Re: when the startup process doesn't (logging startup delays)

On Fri, Sep 03, 2021 at 01:23:56PM +0530, Nitin Jadhav wrote:
> Please find the updated patch attached.

Please check CA+TgmoZtbqxaOLdpNkBcDbz=41tWALA8kpH4M=RWtPYHC7-KNg@mail.gmail.com

I agree with Robert that a standby server should not continuously show timing
messages for WAL replay.

Some doc comments:

+         Sets the time interval between each progress update of the operations
+         performed during startup process. This produces the log message after

Either say "performed by the startup process" or "performed during startup".

s/the/a/

+         every interval of time for the operations that take longer time. The unit

..for those operations which take longer than the specified duration.

+         used to specify the value is seconds. For example, if you set it to
+         <literal> 10s </literal>, then after every <literal> 10s </literal> there

remove "after"

+         is a log message indicating which operation is going on and what is the

say "..every 10s, a log is emitted indicating which operation is ongoing, and
the elapsed time from the beginning of the operation.."

+         elapsed time from beginning. If the value is set to <literal> 0 </literal>,
+         then it logs all the available messages for such operations. <literal> -1

"..then all messages for such operations are logged."

+         </literal> disables the feature. The default value is set to <literal> 10s
+         </literal>

"The default value is >10s<."