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

Justin Pryzby <pryzby@telsasoft.com>

From: Justin Pryzby <pryzby@telsasoft.com>

To: Nitin Jadhav <nitinjadhavpostgres@gmail.com>

Cc: Tom Lane <tgl@sss.pgh.pa.us>, Robert Haas <robertmhaas@gmail.com>, Andres Freund <andres@anarazel.de>, Stephen Frost <sfrost@snowman.net>, Magnus Hagander <magnus@hagander.net>, Thomas Munro <thomas.munro@gmail.com>, pgsql-hackers@postgresql.org

Date: 2021-06-17T12:52:54Z

Lists: pgsql-hackers

+ * Codes of the operations performed during startup process
+ */
+typedef enum StartupProcessOp
+{
+       SYNCFS_IN_PROGRESS,
+       FSYNC_IN_PROGRESS,
+       RECOVERY_IN_PROGRESS,
+       RESET_UNLOGGED_REL_IN_PROGRESS,
+       DUMMY,
+       SYNCFS_END,
+       FSYNC_END,
+       RECOVERY_END,
+       RESET_UNLOGGED_REL_END
+} StartupProcessOp;

What is DUMMY about ?  If you just want to separate the "start" from "end",
you could write:

/* codes for start of operations */
FSYNC_IN_PROGRESS
SYNCFS_IN_PROGRESS
...
/* codes for end of operations */
FSYNC_END
SYNCFS_END
...

Or group them together like:

FSYNC_IN_PROGRESS,
FSYNC_END,
SYNCFS_IN_PROGRESS, 
SYNCFS_END,
RECOVERY_IN_PROGRESS,
RECOVERY_END,
RESET_UNLOGGED_REL_IN_PROGRESS,
RESET_UNLOGGED_REL_END,

-- 
Justin

Commits

Un-revert "Disable STARTUP_PROGRESS_TIMEOUT in standby mode."
- ecb01e6ebb5a 15.3 landed
Revert "Disable STARTUP_PROGRESS_TIMEOUT in standby mode."
- 1eadfbdd7eb0 15.2 landed
Disable STARTUP_PROGRESS_TIMEOUT in standby mode.
- 98e7234242a6 15.2 landed
- 8a2f783cc489 16.0 landed
Fix race condition in startup progress reporting.
- 5ccceb2946d4 15.0 landed
Report progress of startup operations that take a long time.
- 9ce346eabf35 15.0 landed
Add enable_timeout_every() to fire the same timeout repeatedly.
- 732e6677a667 15.0 landed