RE: BUG #18898: replication process not working... sometimes

Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com>

From: "Hayato Kuroda (Fujitsu)" <kuroda.hayato@fujitsu.com>
To: "jcasanov@systemguards.com.ec" <jcasanov@systemguards.com.ec>
Cc: "pgsql-bugs@lists.postgresql.org" <pgsql-bugs@lists.postgresql.org>
Date: 2025-04-18T12:31:07Z
Lists: pgsql-bugs

Attachments

Dear Jaime,

> The following bug has been logged on the website:

Thanks for reporting the issue. Could you please provide scripts which can
reproduce the issue? This is very helpful to analyze and fix.

I roughly emulated the situation like attached but I could not reproduce. Maybe
it missed something.

> Any way to debug the real problem here? or is there something i'm missing?

Not sure it is related, but I could come up with [1] and [2]. This issue could happen
when ALTER PUBLICATION or ALTER TYPE commands are run during the replication.

[1]: https://www.postgresql.org/message-id/flat/de52b282-1166-1180-45a2-8d8917ca74c6%40enterprisedb.com
[2]: https://github.com/postgres/postgres/commit/4909b38af034fa4d2c67c5c71fd8509f870c1695

Best regards,
Hayato Kuroda
FUJITSU LIMITED

Commits

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