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

From: Alexey Makhmutov <a(dot)makhmutov(at)postgrespro(dot)ru>
To: shveta malik <shveta(dot)malik(at)gmail(dot)com>, "Drouvot, Bertrand" <bertranddrouvot(dot)pg(at)gmail(dot)com>, Ajin Cherian <itsajin(at)gmail(dot)com>
Cc: 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-22 13:29:37
Message-ID: d9e1c765-7f83-4015-ade3-16506854d0b1@postgrespro.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

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,
Alexey

Attachment Content-Type Size
0001-Use-only-replayed-position-as-target-flush-point-2.patch text/x-patch 3.2 KB

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Chris Gooch 2025-05-22 14:55:39 GSS Auth issue when user member of lots of AD groups
Previous Message Hayato Kuroda (Fujitsu) 2025-05-22 12:59:52 RE: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5