pgsql: Fix handling of updated tuples in the MERGE statement - Mailing list pgsql-committers

From Alexander Korotkov
Subject pgsql: Fix handling of updated tuples in the MERGE statement
Date
Msg-id E1vyD0n-002Y55-0O@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
Fix handling of updated tuples in the MERGE statement

This branch missed the IsolationUsesXactSnapshot() check.  That led to EPQ on
repeatable read and serializable isolation levels.  This commit fixes the
issue and provides a simple isolation check for that.  Backpatch through v15
where MERGE statement was introduced.

Reported-by: Tender Wang <tndrwang@gmail.com>
Discussion: https://postgr.es/m/CAPpHfdvzZSaNYdj5ac-tYRi6MuuZnYHiUkZ3D-AoY-ny8v%2BS%2Bw%40mail.gmail.com
Author: Tender Wang <tndrwang@gmail.com>
Reviewed-by: Dean Rasheed <dean.a.rasheed@gmail.com>
Backpatch-through: 15

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/177037341a4414f1089748686af9ce8bd9f8d383

Modified Files
--------------
src/backend/executor/nodeModifyTable.c       |  5 +++++
src/test/isolation/expected/merge-update.out | 33 ++++++++++++++++++++++++++++
src/test/isolation/specs/merge-update.spec   |  2 ++
3 files changed, 40 insertions(+)


pgsql-committers by date:

Previous
From: Fujii Masao
Date:
Subject: pgsql: Improve validation of recovery_target_xid GUC values.
Next
From: Alexander Korotkov
Date:
Subject: pgsql: Fix handling of updated tuples in the MERGE statement