mirror of
https://github.com/postgres/postgres.git
synced 2025-04-24 10:47:04 +03:00
Fix a few more redundant calls of GetLatestSnapshot()
Commit 2367503177 fixed this in RelationFindReplTupleByIndex(), but I missed two other similar cases. Per report from Ranier Vilela. Discussion: https://www.postgresql.org/message-id/CAEudQArUT1dE45WN87F-Gb7XMy_hW6x1DFd3sqdhhxP-RMDa0Q@mail.gmail.com Backpatch-through: 13
This commit is contained in:
parent
2367503177
commit
f7c566a1a2
@ -411,7 +411,7 @@ retry:
|
|||||||
|
|
||||||
PushActiveSnapshot(GetLatestSnapshot());
|
PushActiveSnapshot(GetLatestSnapshot());
|
||||||
|
|
||||||
res = table_tuple_lock(rel, &(outslot->tts_tid), GetLatestSnapshot(),
|
res = table_tuple_lock(rel, &(outslot->tts_tid), GetActiveSnapshot(),
|
||||||
outslot,
|
outslot,
|
||||||
GetCurrentCommandId(false),
|
GetCurrentCommandId(false),
|
||||||
lockmode,
|
lockmode,
|
||||||
@ -468,7 +468,7 @@ retry:
|
|||||||
|
|
||||||
PushActiveSnapshot(GetLatestSnapshot());
|
PushActiveSnapshot(GetLatestSnapshot());
|
||||||
|
|
||||||
res = table_tuple_lock(rel, &conflictTid, GetLatestSnapshot(),
|
res = table_tuple_lock(rel, &conflictTid, GetActiveSnapshot(),
|
||||||
*conflictslot,
|
*conflictslot,
|
||||||
GetCurrentCommandId(false),
|
GetCurrentCommandId(false),
|
||||||
LockTupleShare,
|
LockTupleShare,
|
||||||
|
Loading…
x
Reference in New Issue
Block a user