Home > mailing lists

Re: table_tuple_lock's snapshot argument - Mailing list pgsql-hackers

From	Ranier Vilela
Subject	Re: table_tuple_lock's snapshot argument
Date	March 10 19:55:41
Msg-id	CAEudQArUT1dE45WN87F-Gb7XMy_hW6x1DFd3sqdhhxP-RMDa0Q@mail.gmail.com Whole thread Raw
In response to	Re: table_tuple_lock's snapshot argument (Heikki Linnakangas <hlinnaka@iki.fi>)
List	pgsql-hackers

Tree view

Em seg., 10 de mar. de 2025 às 13:52, Heikki Linnakangas <hlinnaka@iki.fi> escreveu:

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.

Thanks.

best regards,

Ranier Vilela

pgsql-hackers by date:

From: Heikki Linnakangas
Date: 10 March, 19:52:50
Subject: Re: table_tuple_lock's snapshot argument

From: Sami Imseih
Date: 10 March, 20:20:57
Subject: Re: Query ID Calculation Fix for DISTINCT / ORDER BY and LIMIT / OFFSET

Re: table_tuple_lock's snapshot argument - Mailing list pgsql-hackers

Previous

Next