Re: Standby server with cascade logical replication could not be properly stopped under load

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Ajin Cherian <itsajin(at)gmail(dot)com>
Cc: Alexey Makhmutov <a(dot)makhmutov(at)postgrespro(dot)ru>, Bertrand Drouvot <bertranddrouvot(dot)pg(at)gmail(dot)com>, shveta malik <shveta(dot)malik(at)gmail(dot)com>, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: Standby server with cascade logical replication could not be properly stopped under load
Date: 2025-05-29 23:32:05
Message-ID: aDjudRqTXYJCt3VT@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message vignesh C 2025-05-30 04:01:19 Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5
Previous Message Jacob Champion 2025-05-29 23:17:16 Re: [EXT] Re: GSS Auth issue when user member of lots of AD groups