On Tue, Mar 7, 2023 at 4:49 PM Ryo Yamaji (Fujitsu)
wrote:
>
> From: Tom Lane
> > I don't see a bug here, or at least I'm not willing to move the goalposts
> > to where you want them to be.
> > I believe that we do guarantee arrival-order locking of individual tuple
> > versions. However, in t
From: Tom Lane
> I don't see a bug here, or at least I'm not willing to move the goalposts to
> where you want them to be.
> I believe that we do guarantee arrival-order locking of individual tuple
> versions. However, in the
> example you show, a single row is being updated over and over. S
"Ryo Yamaji (Fujitsu)" writes:
> In pgql-general, I reported that the queue order changed in
> the following cases. [1]
> $B!&(BMultiple sessions request row locks for the same tuple
> $B!&(BUpdate occurs for target tuple
> I would like to hear the opinion of experts on whether it is a
> spec
Hi all,
In pgql-general, I reported that the queue order changed in
the following cases. [1]
・Multiple sessions request row locks for the same tuple
・Update occurs for target tuple
I would like to hear the opinion of experts on whether it is a
specification or a bug.
I think row locking is a FI
