Re: Visibility bug in tuple lock

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