| From: | Jeff Davis <pgsql(at)j-davis(dot)com> |
|---|---|
| To: | Peter Geoghegan <pg(at)bowt(dot)ie> |
| Cc: | Robins Tharakan <tharakan(at)gmail(dot)com>, PostgreSQL mailing lists <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: PANIC in heap_delete during ALTER TABLE |
| Date: | 2022-09-08 17:30:05 |
| Message-ID: | ccf5707c1d835c0f7ed69b28566e4cc4d7f37189.camel@j-davis.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Wed, 2022-09-07 at 15:44 -0700, Peter Geoghegan wrote:
> This certainly vindicates Tom's decision to backpatch his fix for the
> heap_update() issue. Clearly this new variant bug can't have anything
> to do
> with the 14-era behavioral change to lazy_vacuum_heap_page() from
> commit 8523492d4e. That behavioral change was clearly a factor in the
> heap_update() issue, but can't be relevant here. Since the repro we
> have
> shows that 13 is also affected.
I wasn't able to repro on 13, but Robins' report indicates that it's
possible.
Regards,
Jeff Davis
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2022-09-08 18:36:47 | Re: BUG #17610: Use of multiple composite types incompatible with record-typed function parameter |
| Previous Message | Tom Lane | 2022-09-08 16:17:14 | Re: BUG #17610: Use of multiple composite types incompatible with record-typed function parameter |