Re: Improve handling of parameter differences in physical replication

From: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
To: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Improve handling of parameter differences in physical replication
Date: 2020-03-09 09:42:21
Message-ID: b03eacca-1368-6a05-ee3d-82f8dd63b3bb@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Kyotaro Horiguchi 2020-03-09 09:44:41 Re: Identifying user-created objects
Previous Message Peter Eisentraut 2020-03-09 09:27:46 Re: [PATCH] Support built control file in PGXS VPATH builds