| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Peter Geoghegan <pg(at)bowt(dot)ie> |
| Cc: | Jaime Casanova <jcasanov(at)systemguards(dot)com(dot)ec>, pgsql-committers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: pgsql: Avoid improbable PANIC during heap_update. |
| Date: | 2022-09-30 23:52:44 |
| Message-ID: | 841352.1664581964@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
Peter Geoghegan <pg(at)bowt(dot)ie> writes:
> On Fri, Sep 30, 2022 at 2:56 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Could be, because we haven't seen field reports of this in v14 yet.
> I would be more confident here were it not for the recent
> heap_delete() issue reported by one of my AWS colleagues (and fixed by
> another, Jeff Davis). See commit 163b0993 if you missed it before now.
Hmm, okay, though that's really a distinct bug of the same ilk.
You're right that I'd not paid close attention to that thread after
Jeff diagnosed the problem. It does seem like Robins' report
shows that there's some way that v13 will set the AV bit without
a cleanup lock ... does that constitute a bug in itself?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2022-10-01 00:09:50 | Re: pgsql: Avoid improbable PANIC during heap_update. |
| Previous Message | Tom Lane | 2022-09-30 23:37:19 | pgsql: Avoid improbable PANIC during heap_update, redux. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2022-10-01 00:09:50 | Re: pgsql: Avoid improbable PANIC during heap_update. |
| Previous Message | Nathan Bossart | 2022-09-30 23:18:34 | Re: predefined role(s) for VACUUM and ANALYZE |