Re: Standby server with cascade logical replication could not be properly stopped under load
От | Bertrand Drouvot |
---|---|
Тема | Re: Standby server with cascade logical replication could not be properly stopped under load |
Дата | |
Msg-id | aC9DXHt/MwFCW6Is@ip-10-97-1-34.eu-west-3.compute.internal обсуждение исходный текст |
Ответ на | Re: Standby server with cascade logical replication could not be properly stopped under load (shveta malik <shveta.malik@gmail.com>) |
Ответы |
Re: Standby server with cascade logical replication could not be properly stopped under load
|
Список | 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 по дате отправления: