Thanks, for looking into this and for creating the patch.
> +1 for that approach. heap_lock_updated_tuple() actually does that check
> too, but not for the first tuple.
I think this will for sure fix the problem, however we are still
accessing completely unrelated tuples. It feels unsafe to acces
On 13/10/2025 10:48, Jasper Smit wrote:
We found a bug in heap_lock_tuple(). It seems to be unsafe to follow
the t_ctid pointer of updated tuples,
in the presence of aborted tuples. Vacuum can mark aborted tuples
LP_UNUSED, even if there are still
visible tuples that have a t_ctid pointing to
