From: Robert Haas <rhaas@postgresql.org>
To: pgsql-committers@lists.postgresql.org
Subject: pgsql: Disable STARTUP_PROGRESS_TIMEOUT in standby mode.
Date: Mon, 06 Feb 2023 16:01:35 +0000
Message-ID: <E1pP3vy-001tXF-FV@gemulon.postgresql.org> (raw)
Disable STARTUP_PROGRESS_TIMEOUT in standby mode.
In standby mode, we don't actually report progress of recovery,
but up until now, startup_progress_timeout_handler() nevertheless
got called every log_startup_progress_interval seconds. That's
an unnecessary expense, so avoid it.
Report by Thomas Munro. Patch by Bharath Rupireddy, reviewed by
Simon Riggs, Thomas Munro, and me. Back-patch to v15, where
the problem was introduced.
Discussion: https://www.postgresql.org/message-id/CA%2BhUKGKCHSffAj8zZJKJvNX7ygnQFxVD6wm1d-2j3fVw%2BMafPQ%40mail...
Branch
------
master
Details
-------
https://git.postgresql.org/pg/commitdiff/8a2f783cc489e4e1820163c1c439125aad4d7a92
Modified Files
--------------
src/backend/access/transam/xlogrecovery.c | 25 ++++++++++++++++++++++---
src/backend/postmaster/startup.c | 30 +++++++++++++++++++++++++++---
src/include/postmaster/startup.h | 2 ++
3 files changed, 51 insertions(+), 6 deletions(-)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-committers@postgresql.org
Cc: rhaas@postgresql.org
Subject: Re: pgsql: Disable STARTUP_PROGRESS_TIMEOUT in standby mode.
In-Reply-To: <E1pP3vy-001tXF-FV@gemulon.postgresql.org>
References: <E1pP3vy-001tXF-FV@gemulon.postgresql.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox