Re: Logical replication: lost updates/deletes and invalid log messages caused by SnapshotDirty + concurrent updates - Mailing list pgsql-hackers

From Mihail Nikalayeu
Subject Re: Logical replication: lost updates/deletes and invalid log messages caused by SnapshotDirty + concurrent updates
Date
Msg-id CADzfLwV9hJXzM-_e1JP4pp0Oub6wv=QoY=FsifJ+VXiyPFbCSQ@mail.gmail.com
Whole thread Raw
In response to Logical replication: lost updates/deletes and invalid log messages caused by SnapshotDirty + concurrent updates  (Mihail Nikalayeu <mihailnikalayeu@gmail.com>)
List 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.



pgsql-hackers by date:

Previous
From: Álvaro Herrera
Date:
Subject: Re: contrib/sepgsql regression tests have been broken for months
Next
From: Alexander Lakhin
Date:
Subject: Re: Instability of phycodorus in pg_upgrade tests with JIT