Re: BUG #17462: Invalid memory access in heapam_tuple_lock - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #17462: Invalid memory access in heapam_tuple_lock
Date
Msg-id 530434.1649707170@sss.pgh.pa.us
Whole thread Raw
In response to Re: BUG #17462: Invalid memory access in heapam_tuple_lock  (Andres Freund <andres@anarazel.de>)
Responses Re: BUG #17462: Invalid memory access in heapam_tuple_lock  (Andres Freund <andres@anarazel.de>)
List pgsql-bugs
Andres Freund <andres@anarazel.de> writes:
> On 2022-04-11 15:25:12 -0400, Tom Lane wrote:
>> That seems like a fairly clean idea, although I think we can't use it
>> in the back branches without an ABI break.  We're not going to find a
>> TID's worth of padding space in struct SnapshotData.

> I guess we could put members of SnapshotData into a union with ItemPointerData
> that aren't used by InitDirtySnapshot()/HeapTupleSatisfiesDirty().

Yeah, that could work.  You want to draft a patch, or shall I?

            regards, tom lane



pgsql-bugs by date:

Previous
From: Andres Freund
Date:
Subject: Re: BUG #17462: Invalid memory access in heapam_tuple_lock
Next
From: Andres Freund
Date:
Subject: Re: BUG #17462: Invalid memory access in heapam_tuple_lock