Re: ri_LockPKTuple misleading message - Mailing list pgsql-hackers

From Amit Langote
Subject Re: ri_LockPKTuple misleading message
Date
Msg-id CA+HiwqGF_myog4OcQ+39CnFzS8iODS+YeGDNw9UfU_OxyNjvcA@mail.gmail.com
Whole thread
In response to Re: ri_LockPKTuple misleading message  (Andres Freund <andres@anarazel.de>)
Responses Re: ri_LockPKTuple misleading message
List pgsql-hackers
Hi Andres,

On Sat, Apr 25, 2026 at 10:38 PM Andres Freund <andres@anarazel.de> wrote:
> On 2026-04-25 20:59:50 +0900, Amit Langote wrote:
> > On Sat, Apr 25, 2026 at 20:42 Junwang Zhao <zhjwpku@gmail.com> wrote:
> >
> > > On Sat, Apr 25, 2026 at 7:31 PM Amit Langote <amitlangote09@gmail.com>
> > > I have a feeling we should also update ExecLockRows(), since the
> > > TM_Deleted branches in other places seem to use the wording
> > > "concurrent delete".
> > >
> > > cc andres since he was the original author of this code.
> > >
> > >
> > > https://github.com/postgres/postgres/blob/REL_12_STABLE/src/backend/executor/nodeLockRows.c#L230
> >
> > Ah, OK, then let's change both instances for consistency, unless Andres
> > remembers a reason not to.
> >
> > Thanks Junwang for checking that.
>
> No, I can't see any reason for that.  I assume it was a copy & paste error,
> but it's hard to know this far back.

Thanks for chiming in.

Here is a patch to fix both instances.  I'll leave the ExecLockRows()
instances unchanged in the back-branches due to the lack of user
complaints.

--
Thanks, Amit Langote

Attachment

pgsql-hackers by date:

Previous
From: "Hayato Kuroda (Fujitsu)"
Date:
Subject: RE: Adding REPACK [concurrently]
Next
From: Tatsuo Ishii
Date:
Subject: Re: Row pattern recognition