| 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, Jeff Davis <pgsql(at)j-davis(dot)com> |
| Subject: | Re: pgsql: Avoid improbable PANIC during heap_update. |
| Date: | 2022-10-01 05:13:13 |
| Message-ID: | 873099.1664601193@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:
> I think that the heap_delete() issue is probably in all PG versions.
Yeah, that's what I'm afraid of ...
> I am not aware of any reason why we should need the heap_update()
> fixes to be backpatched any further.
How so? AFAICS these are exactly the same oversight, ie failure
to deal with the all-visible bit getting set partway through the
operation. You've explained how that can happen.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2022-10-01 05:25:06 | Re: pgsql: Avoid improbable PANIC during heap_update. |
| Previous Message | Peter Geoghegan | 2022-10-01 05:09:19 | Re: pgsql: Avoid improbable PANIC during heap_update. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2022-10-01 05:25:06 | Re: pgsql: Avoid improbable PANIC during heap_update. |
| Previous Message | Peter Geoghegan | 2022-10-01 05:09:19 | Re: pgsql: Avoid improbable PANIC during heap_update. |