Horton

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

Robert Haas <robertmhaas@gmail.com>

View thread View on postgr.es
From: Robert Haas <robertmhaas@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>, Kyotaro Horiguchi <horikyota.ntt@gmail.com>, simon.riggs@enterprisedb.com, thomas.munro@gmail.com, nitinjadhavpostgres@gmail.com, alvherre@alvh.no-ip.org, pryzby@telsasoft.com, michael@paquier.xyz, andres@anarazel.de, sfrost@snowman.net, magnus@hagander.net, pgsql-hackers@postgresql.org
Date: 2023-02-06T16:08:56Z
Lists: pgsql-hackers 
On Mon, Feb 6, 2023 at 11:07 AM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Umm ... is this really the sort of patch to be committing on a
> release wrap day?

Oh, shoot, I wasn't thinking about that. Would you like me to revert
it in v15 for now?

-- 
Robert Haas
EDB: http://www.enterprisedb.com

Commits

  1. Un-revert "Disable STARTUP_PROGRESS_TIMEOUT in standby mode."

  2. Revert "Disable STARTUP_PROGRESS_TIMEOUT in standby mode."

  3. Disable STARTUP_PROGRESS_TIMEOUT in standby mode.

  4. Fix race condition in startup progress reporting.

  5. Report progress of startup operations that take a long time.

  6. Add enable_timeout_every() to fire the same timeout repeatedly.