Horton
Menu

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

Alexey Makhmutov <a.makhmutov@postgrespro.ru>

View thread
From: Alexey Makhmutov <a.makhmutov@postgrespro.ru>
To: shveta malik <shveta.malik@gmail.com>, "Drouvot, Bertrand" <bertranddrouvot.pg@gmail.com>, Ajin Cherian <itsajin@gmail.com>
Cc: pgsql-bugs@lists.postgresql.org
Date: 2025-05-22T13:29:37Z
Lists: pgsql-bugs

Attachments

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

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Use replay LSN as target for cascading logical WAL senders