| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | anisimow(dot)d(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #17462: Invalid memory access in heapam_tuple_lock |
| Date: | 2022-04-11 20:32:03 |
| Message-ID: | 20220411203203.avlrzwy526j4yfas@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Hi,
On 2022-04-11 15:59:30 -0400, Tom Lane wrote:
> Andres Freund <andres(at)anarazel(dot)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?
If you would, I'd appreciate it. I've to finish a talk I'm giving tomorrow,
and I want to fix the recovery conflict bug - it's triggering the bug like
half the time on CI...
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2022-04-11 23:07:31 | Re: BUG #17462: Invalid memory access in heapam_tuple_lock |
| Previous Message | Tom Lane | 2022-04-11 19:59:30 | Re: BUG #17462: Invalid memory access in heapam_tuple_lock |