| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
| Cc: | thomas(dot)d(dot)mckay(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #17607: Server process crashes when PLpgSQL function raises error in subtransaction |
| Date: | 2022-09-25 20:34:05 |
| Message-ID: | 3136668.1664138045@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
... and after yet more poking at it, I see why c5b7ba4e6 masked
the problem: it added an optimization such that we don't use the
storeslot at all unless a tuple mapping conversion is required.
That led me to the test case shown in the attached, which exhibits
this symptom in all branches since v12.
I had been planning to let this wait until after 15rc1 wrap,
but now that I have evidence that the bug is still live in v15,
I'm going to go ahead and push. Both components of the fix
seem like extremely safe changes, even for the day before wrap.
regards, tom lane
| Attachment | Content-Type | Size |
|---|---|---|
| fix-trigger-tupdesc-refcount-issue-3.patch | text/x-diff | 7.7 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Bug reporting form | 2022-09-26 03:00:41 | BUG #17622: a potential bug of NPD |
| Previous Message | Tom Lane | 2022-09-25 19:01:15 | Re: BUG #17607: Server process crashes when PLpgSQL function raises error in subtransaction |