Re: pg_rewind vs superuser - Mailing list pgsql-hackers

From Magnus Hagander
Subject Re: pg_rewind vs superuser
Date
Msg-id CABUevEyc_4gLZSFDacsbC=Jy_-rEhM4zOd3Gr=7OdA3pBZAK2g@mail.gmail.com
Whole thread Raw
In response to Re: pg_rewind vs superuser  (Michael Paquier <michael@paquier.xyz>)
Responses Re: pg_rewind vs superuser  (Michael Paquier <michael@paquier.xyz>)
List pgsql-hackers


On Fri, Apr 5, 2019 at 10:06 AM Michael Paquier <michael@paquier.xyz> wrote:
On Fri, Apr 05, 2019 at 09:59:29AM +0200, Magnus Hagander wrote:
> A related question is, could we (for 12+) actually make the problem go
> away? As in, can we detect the state and just have pg_rewind issue the
> checkpoint as needed?

I am not sure as you can still bump into the legit case where one is
trying to rewind an instance which is on the same timeline as the
source, and nothing should happen in this case.

If that is the case, would running a CHECKPOINT actually cause a problem?

 
--

pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: pg_rewind vs superuser
Next
From: Kyotaro HORIGUCHI
Date:
Subject: Re: Protect syscache from bloating with negative cache entries