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

From Alexey Makhmutov
Subject Re: Standby server with cascade logical replication could not be properly stopped under load
Date
Msg-id f2575904-acfe-4037-9748-61fdb4a7abe4@postgrespro.ru
Whole thread Raw
In response to Re: Standby server with cascade logical replication could not be properly stopped under load  (Bertrand Drouvot <bertranddrouvot.pg@gmail.com>)
List pgsql-bugs
Hi Bertrand, thank you for looking at this issue.

On 5/22/25 18:31, Bertrand Drouvot wrote:
> 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.

I've tried to update method comment as well in the updated patch: 
0001-Use-only-replayed-position-as-target-flush-point-3-pg-master.patch.
The same patch could be applied on top of PG 17 as well.

PG 16 does not have the slot synchronization logic, so its 
implementation of GetStandbyFlushRecPtr is slightly different and 
comments need to be updated to reflect this discrepancy as well. So, 
here is a variant of the same patch updated to be compatible with PG 16: 
0002-Use-only-replayed-position-as-target-flush-point-3-pg-16.patch

Thanks,
Alexey

Attachment

pgsql-bugs by date:

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