Re: Visibility bug in tuple lock - Mailing list pgsql-hackers

From Heikki Linnakangas
Subject Re: Visibility bug in tuple lock
Date
Msg-id a318decf-af6d-4e77-8d3a-96c8ff7150c1@iki.fi
Whole thread Raw
In response to Re: Visibility bug in tuple lock  (Jasper Smit <jbsmit@gmail.com>)
List pgsql-hackers
On 18/12/2025 11:56, Jasper Smit wrote:
> The test is really nice with the injection points and the dynamically
> sized data.
> 
>> Ah, but this codepath is taken when HEAP_KEYS_UPDATED is *not* set. I
>> got that backwards. So I agree the ItemPointerEquals(&tuple->t_self,
>> ctid) check is redundant.
> 
> Ok, I did not think about deletes. So the boolean updated here could
> mean both update and delete, that makes sense to me.

Committed and backpatched this now. Thanks!

- Heikki




pgsql-hackers by date:

Previous
From: lakshmi
Date:
Subject: Re: Use log_newpage_range in HASH index build
Next
From: Dilip Kumar
Date:
Subject: Re: Proposal: Conflict log history table for Logical Replication