Re: pg_rewind after promote

2024-03-28 Thread Laurenz Albe
On Thu, 2024-03-28 at 17:17 +0100, Emond Papegaaij wrote: > Op do 28 mrt 2024 om 16:21 schreef Laurenz Albe : > > 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 ign

Re: pg_rewind after promote

2024-03-28 Thread Emond Papegaaij
Op do 28 mrt 2024 om 16:21 schreef Laurenz Albe : > On Thu, 2024-03-28 at 15:52 +0100, Emond Papegaaij wrote: > > This works fine most of the time, but sometimes we see this message on > one of the nodes: > > pg_rewind: source and target cluster are on the same timeline pg_rewind: > no rewind requ

Re: pg_rewind after promote

2024-03-28 Thread Laurenz Albe
On Thu, 2024-03-28 at 15:52 +0100, Emond Papegaaij wrote: >  * we detach the primary database backend, forcing a failover >  * pgpool selects a new primary database and promotes it >  * the other 2 nodes (the old primary and the other standby) are rewound >and streaming is resumed from the new