From f7c566a1a276c5f228891c7599df1c0b8878eb35 Mon Sep 17 00:00:00 2001 From: Heikki Linnakangas Date: Mon, 10 Mar 2025 18:54:58 +0200 Subject: [PATCH] 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 --- src/backend/executor/execReplication.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/backend/executor/execReplication.c b/src/backend/executor/execReplication.c index 69109a75726..f59cb9098ff 100644 --- a/src/backend/executor/execReplication.c +++ b/src/backend/executor/execReplication.c @@ -411,7 +411,7 @@ retry: PushActiveSnapshot(GetLatestSnapshot()); - res = table_tuple_lock(rel, &(outslot->tts_tid), GetLatestSnapshot(), + res = table_tuple_lock(rel, &(outslot->tts_tid), GetActiveSnapshot(), outslot, GetCurrentCommandId(false), lockmode, @@ -468,7 +468,7 @@ retry: PushActiveSnapshot(GetLatestSnapshot()); - res = table_tuple_lock(rel, &conflictTid, GetLatestSnapshot(), + res = table_tuple_lock(rel, &conflictTid, GetActiveSnapshot(), *conflictslot, GetCurrentCommandId(false), LockTupleShare,