Re: Logical replication: lost updates/deletes and invalid log messages caused by SnapshotDirty + concurrent updates

From: Mihail Nikalayeu <mihailnikalayeu(at)gmail(dot)com>
To: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
Cc: Andres Freund <andres(at)anarazel(dot)de>
Subject: Re: Logical replication: lost updates/deletes and invalid log messages caused by SnapshotDirty + concurrent updates
Date: 2025-10-25 15:46:00
Message-ID: CADzfLwV9hJXzM-_e1JP4pp0Oub6wv=QoY=FsifJ+VXiyPFbCSQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hello, everyone!

Andres, added you in CC because I am referring to your words in
personal conversation.

Amit, I asked Andres about that situation and Andres said it is a bug
if we execute DirtySnapshot without holding a real one.
And this is how it is done in RelationFindReplTupleByIndex and
RelationFindReplTupleSeq now.

Best regards,
Mikhail.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Alexander Lakhin 2025-10-25 16:00:00 Re: Instability of phycodorus in pg_upgrade tests with JIT
Previous Message Álvaro Herrera 2025-10-25 15:29:25 Re: contrib/sepgsql regression tests have been broken for months