| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
| Cc: | exclusion(at)gmail(dot)com, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: fix crash with Python 3.11 |
| Date: | 2022-02-24 18:17:38 |
| Message-ID: | 1490937.1645726658@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
I wrote:
> * It might be a good idea to add parallel test cases for the other PLs.
As I suspected, plperl and pltcl show exactly the same problems
when trapping a failure at commit, reinforcing my opinion that this
is a SPI bug that needs to be fixed in SPI. (plpgsql is not subject
to this problem, because its only mechanism for trapping errors is
a BEGIN block, ie a subtransaction, so it won't get to the interesting
part.) They do have logic to catch the thrown error, though, so no
additional fix is needed in either once we fix the core code.
v2 attached adds those test cases.
regards, tom lane
| Attachment | Content-Type | Size |
|---|---|---|
| start-new-xact-in-SPI-commit-rollback-2.patch | text/x-diff | 26.3 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2022-02-24 18:24:30 | Re: JSON path decimal literal syntax |
| Previous Message | Nathan Bossart | 2022-02-24 17:55:53 | Re: remove more archiving overhead |