Re: Standby server with cascade logical replication could not be properly stopped under load - Mailing list pgsql-bugs

From Michael Paquier
Subject Re: Standby server with cascade logical replication could not be properly stopped under load
Date
Msg-id aDjudRqTXYJCt3VT@paquier.xyz
Whole thread Raw
In response to Re: Standby server with cascade logical replication could not be properly stopped under load  (Ajin Cherian <itsajin@gmail.com>)
List pgsql-bugs
On Thu, May 29, 2025 at 08:28:01PM +1000, Ajin Cherian wrote:
> I think this new fix is much better and cleaner. A suggestion for the
> comment:
> "For cascading logical WAL senders, we use the replay LSN instead of the
> flush LSN, since logical decoding on a standby only processes WAL that has
> been replayed. This distinction becomes particularly important during
> shutdown, as new WAL is no longer replayed and the last replayed LSN marks
> the furthest point up to which decoding can proceed."

Yes, that sounds better than my previous suggestion.  Thanks.
--
Michael

Attachment

pgsql-bugs by date:

Previous
From: Jacob Champion
Date:
Subject: Re: [EXT] Re: GSS Auth issue when user member of lots of AD groups
Next
From: vignesh C
Date:
Subject: Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5