pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andres Freund <andres@anarazel.de>
Cc: anisimow.d@gmail.com
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17462: Invalid memory access in heapam_tuple_lock
Date: Mon, 11 Apr 2022 15:59:30 -0400
Message-ID: <530434.1649707170@sss.pgh.pa.us> (raw)
In-Reply-To: <20220411194051.sovwssdawxoh4m5h@alap3.anarazel.de>
References: <17462-9c98a0f00df9bd36@postgresql.org>
	<286748.1649692519@sss.pgh.pa.us>
	<288544.1649693991@sss.pgh.pa.us>
	<20220411173417.ocwjn5xrkqqjiysl@alap3.anarazel.de>
	<352840.1649699498@sss.pgh.pa.us>
	<20220411190042.o5ebdhc5qsejleff@alap3.anarazel.de>
	<496872.1649705112@sss.pgh.pa.us>
	<20220411194051.sovwssdawxoh4m5h@alap3.anarazel.de>

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





view thread (15+ messages)  latest in thread

Message-ID: <530434.1649707170@sss.pgh.pa.us>
Permalink:  ../530434.1649707170@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/530434.1649707170@sss.pgh.pa.us

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-bugs@postgresql.org
  Cc: tgl@sss.pgh.pa.us, andres@anarazel.de, anisimow.d@gmail.com, pgsql-bugs@lists.postgresql.org
  Subject: Re: BUG #17462: Invalid memory access in heapam_tuple_lock
  In-Reply-To: <530434.1649707170@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox