From: Laurenz Albe <laurenz.albe@cybertec.at>
To: Emond Papegaaij <emond.papegaaij@gmail.com>
To: pgsql-general@lists.postgresql.org
Subject: Re: pg_rewind after promote
Date: Thu, 28 Mar 2024 23:01:52 +0100
Message-ID: <e7b16ddea93a92575cb6d143b6ef602cab22432e.camel@cybertec.at> (raw)
In-Reply-To: <CAGXsc+ZfBqG8b0Q_NcGgSf6e03w1xMgQTawzb1ivjbMpWzuChg@mail.gmail.com>
References: <CAGXsc+ZS6=cH2VSERaeNhGtNLosRbFovC0f7ty_BxnPJb0xvOg@mail.gmail.com>
<c552270a77ccf35bef172b5d031955981dd3613c.camel@cybertec.at>
<CAGXsc+ZfBqG8b0Q_NcGgSf6e03w1xMgQTawzb1ivjbMpWzuChg@mail.gmail.com>
On Thu, 2024-03-28 at 17:17 +0100, Emond Papegaaij wrote:
> Op do 28 mrt 2024 om 16:21 schreef Laurenz Albe <laurenz.albe@cybertec.at>:
> > On Thu, 2024-03-28 at 15:52 +0100, Emond Papegaaij wrote:
> > > pg_rewind: source and target cluster are on the same timeline pg_rewind: no rewind required
> > >
> > > If we ignore the response from pg_rewind, streaming will break on the node that reported
> > > no rewind was required. On the new primary, we do observe the database moving from timeline
> > > 21 to 22, but it seems this takes some time to materialize to be observable by pg_rewind.
> >
> > This must be the problem addressed by commit 009eeee746 [1].
> >
> > A temporary workaround could be to explicitly trigger a checkpoint right after
> > promotion.
>
> Would this be as simple as sending a CHECKPOINT to the new primary just after promoting?
> This would work fine for us until we've migrated to v16.
Yes, that would be the idea.
Yours,
Laurenz Albe
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-general@postgresql.org
Cc: laurenz.albe@cybertec.at, emond.papegaaij@gmail.com, pgsql-general@lists.postgresql.org
Subject: Re: pg_rewind after promote
In-Reply-To: <e7b16ddea93a92575cb6d143b6ef602cab22432e.camel@cybertec.at>
* 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