Re: Synchronizing slots from primary to standby

From: Peter Eisentraut <peter(at)eisentraut(dot)org>
To: "Drouvot, Bertrand" <bertranddrouvot(dot)pg(at)gmail(dot)com>, Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, Ashutosh Sharma <ashu(dot)coek88(at)gmail(dot)com>
Cc: Andres Freund <andres(at)anarazel(dot)de>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Synchronizing slots from primary to standby
Date: 2023-07-12 11:48:56
Message-ID: 4e4eec0d-ef0f-20f8-88bf-2151b0341cba@eisentraut.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 14.04.23 15:22, Drouvot, Bertrand wrote:
> Now that the "Minimal logical decoding on standby" patch series
> (mentioned up-thread) has been
> committed, I think we can resume working on this one ("Synchronizing
> slots from primary to standby").

Maybe you have seen this extension that was released a few months ago:
https://github.com/EnterpriseDB/pg_failover_slots . This contains the
same functionality packaged as an extension. Maybe this can give some
ideas about how this should behave and what options to provide etc.

Note that pg_failover_slots doesn't use logical decoding on standby,
because that would be too slow in practice. Earlier in this thread we
had some discussion about which of the two approaches was preferred.
Anyway, that's what's out there.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Justin Pryzby 2023-07-12 11:52:16 Re: pg16b2: REINDEX segv on null pointer in RemoveFromWaitQueue
Previous Message Daniel Gustafsson 2023-07-12 11:47:51 Re: Testing autovacuum wraparound (including failsafe)