From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
To: Masahiko Sawada <masahiko.sawada@2ndquadrant.com>
To: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Subject: Re: Improve handling of parameter differences in physical replication
Date: Mon, 9 Mar 2020 10:45:54 +0100
Message-ID: <ecd7ad33-c4dd-7587-ec0e-87729852bc3e@2ndquadrant.com> (raw)
In-Reply-To: <CA+fd4k4ehrboiEB8GFbe-gpiVyFO_cPE57ZpBhPUgJtpCdhC7Q@mail.gmail.com>
References: <4ad69a4c-cc9b-0dfe-0352-8b1b0cd36c7b@2ndquadrant.com>
<20200228153331.GA31634@alvherre.pgsql>
<CA+fd4k4ehrboiEB8GFbe-gpiVyFO_cPE57ZpBhPUgJtpCdhC7Q@mail.gmail.com>
On 2020-03-09 09:11, Masahiko Sawada wrote:
> I think after recovery is paused users will be better to restart the
> server rather than resume the recovery. I agree with this idea but I'm
> slightly concerned that users might not realize that recovery is
> paused until they look at that line in server log or at
> pg_stat_replication because the standby server is still functional. So
> I think we can periodically send WARNING to inform user that we're
> still waiting for parameter change and restart.
I think that would be annoying, unless you create a system for
configuring those periodic warnings.
I imagine in a case like having set max_prepared_transactions but never
actually using prepared transactions, people will just ignore the
warning until they have their next restart, so it could be months of
periodic warnings.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
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 using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: peter.eisentraut@2ndquadrant.com, masahiko.sawada@2ndquadrant.com, alvherre@2ndquadrant.com
Subject: Re: Improve handling of parameter differences in physical replication
In-Reply-To: <ecd7ad33-c4dd-7587-ec0e-87729852bc3e@2ndquadrant.com>
* 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