Re: ri_LockPKTuple misleading message - Mailing list pgsql-hackers

From Andres Freund
Subject Re: ri_LockPKTuple misleading message
Date
Msg-id 53n4zdnh3277antifpc2iz6h5dxmkax25ei6lldadh5mez2eyb@bc4olaxxjx3t
Whole thread
In response to Re: ri_LockPKTuple misleading message  (Amit Langote <amitlangote09@gmail.com>)
List pgsql-hackers
Hi,

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.

Greetings,

Andres Freund



pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: Adding an explaining title to Notes on SGML
Next
From: Jim Jones
Date:
Subject: Re: Fix bug with accessing to temporary tables of other sessions