Re: pg_rewind vs superuser

Magnus Hagander <magnus@hagander.net>

From: Magnus Hagander <magnus@hagander.net>
To: Michael Paquier <michael@paquier.xyz>
Cc: Michael Banck <mbanck@gmx.net>, PostgreSQL Developers <pgsql-hackers@lists.postgresql.org>
Date: 2019-04-05T08:11:22Z
Lists: 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?


-- 
 Magnus Hagander
 Me: https://www.hagander.net/ <http://www.hagander.net/>
 Work: https://www.redpill-linpro.com/ <http://www.redpill-linpro.com/>

Commits

  1. Fix some documentation in pg_rewind