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

From Bertrand Drouvot
Subject Re: Standby server with cascade logical replication could not be properly stopped under load
Date
Msg-id aC9DXHt/MwFCW6Is@ip-10-97-1-34.eu-west-3.compute.internal
Whole thread Raw
In response to Re: Standby server with cascade logical replication could not be properly stopped under load  (shveta malik <shveta.malik@gmail.com>)
Responses Re: Standby server with cascade logical replication could not be properly stopped under load
List pgsql-bugs
Hi,

On Thu, May 22, 2025 at 04:29:37PM +0300, Alexey Makhmutov wrote:
> Hi Ajin and Shveta, thank you for looking at this issue.
> 
> On 5/22/25 12:48, Ajin Cherian wrote:
> 
> > Just a small comment: can you explicitly mention in the comments that
> > "for logical replication we can only send records that have already
> > been replayed else we might get stuck in shutdown" or something to
> > that effect as that distinction is important for future developers in
> > this area.
> 
> Thank you. I've expanded the comment to make it more verbose to clarify
> expected logic in this case.
> Updated patch is attached as
> '0001-Use-only-replayed-position-as-target-flush-point-2.patch'.

Thanks for the report!

I agree with your analysis and I think that your proposed fix make sense. I
wonder if the comment on top of GetStandbyFlushRecPtr() could be updated a bit
though.

Regards,

-- 
Bertrand Drouvot
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com



pgsql-bugs by date:

Previous
From: Shlok Kyal
Date:
Subject: Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5
Next
From: Tom Lane
Date:
Subject: Re: GSS Auth issue when user member of lots of AD groups