Re: table_tuple_lock's snapshot argument

From: Heikki Linnakangas <hlinnaka(at)iki(dot)fi>
To: Ranier Vilela <ranier(dot)vf(at)gmail(dot)com>
Cc: Alexander Korotkov <aekorotkov(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: table_tuple_lock's snapshot argument
Date: 2025-03-10 16:52:50
Message-ID: db3584c6-c344-4a4c-943e-468a1a08d54d@iki.fi
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 10/03/2025 18:20, Ranier Vilela wrote:
> Just for curiosity.
> *RelationFindReplTupleSeq* on the same source, does not suffer
> from the same issue?
>
> PushActiveSnapshot(GetLatestSnapshot());
>
> res = table_tuple_lock(rel, &(outslot->tts_tid), GetLatestSnapshot(),

:facepalm: yep, it sure does, and FindConflictTuple() too. Thanks, I'll
go fix those too.

--
Heikki Linnakangas
Neon (https://neon.tech)

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Ranier Vilela 2025-03-10 16:55:41 Re: table_tuple_lock's snapshot argument
Previous Message Ranier Vilela 2025-03-10 16:20:54 Re: table_tuple_lock's snapshot argument