From: Peter Eisentraut <peter.eisentraut@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:42:21 +0100
Message-ID: <b03eacca-1368-6a05-ee3d-82f8dd63b3bb@2ndquadrant.com> (raw)
In-Reply-To: <20200228153331.GA31634@alvherre.pgsql>
References: <20200228153331.GA31634@alvherre.pgsql>
On 2020-02-28 16:33, Alvaro Herrera wrote:
> Hmm, so what is the actual end-user behavior? As I read the code, we
> first send the WARNING, then pause recovery until the user resumes
> replication; at that point we raise the original error. Presumably, at
> that point the startup process terminates and is relaunched, and replay
> continues normally. Is that it?
No, at that point you get the original, current behavior that the server
instance shuts down with a fatal error.
--
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, alvherre@2ndquadrant.com
Subject: Re: Improve handling of parameter differences in physical replication
In-Reply-To: <b03eacca-1368-6a05-ee3d-82f8dd63b3bb@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