Logical replication can lose an update after concurrent index invalidation #61
Locked
Replies: 1 comment
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
pgsql-hackersCALDaNm1tEL3x=juBUP5VZCWEARK7bLyf5ugGmWvYwV6OtO=ZpQ@mail.gmail.comOn Thu, 3 Sept 2026 at 16:15, Mihail Nikalayeu
<mihailnikalayeu(at)gmail(dot)com> wrote:
Couple of minor comments:
--- a/src/backend/replication/logical/worker.c
+++ b/src/backend/replication/logical/worker.c
@@ -249,6 +249,7 @@
#include "access/genam.h"
#include "access/commit_ts.h"
+#include "access/htup_details.h"
#include "access/table.h"
a) pgindent shows this needs adjustment:
identifies the row on
it the identity,
CONCURRENTLY can commit
b) similarly here too:
the relation's
replica identity or primary key, rather
than an index usable for a REPLICA
IDENTITY FULL remote relation. Placed
here to fit in existing padding, which
leaves the struct layout unchanged in
back branches. */
Regards,
Vignesh
All reactions