Re: Visibility bug in tuple lock

From: Heikki Linnakangas <hlinnaka(at)iki(dot)fi>
To: Jasper Smit <jbsmit(at)gmail(dot)com>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Visibility bug in tuple lock
Date: 2025-12-23 12:07:48
Message-ID: a318decf-af6d-4e77-8d3a-96c8ff7150c1@iki.fi
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: 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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Dilip Kumar 2025-12-23 12:22:14 Re: Proposal: Conflict log history table for Logical Replication
Previous Message lakshmi 2025-12-23 11:53:07 Re: Use log_newpage_range in HASH index build