| From: | Markus Wanner <markus(dot)wanner(at)enterprisedb(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>, exclusion(at)gmail(dot)com, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: fix crash with Python 3.11 |
| Date: | 2022-06-23 19:57:07 |
| Message-ID: | a63db964-196b-f025-40f3-658b8c8da78b@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 6/23/22 15:34, Tom Lane wrote:
> Under what circumstances would it be OK for outside code to call
> SPICleanup?
For the same reasons previous Postgres versions called SPICleanup: from
a sigsetjmp handler that duplicates most of what Postgres does in such a
situation.
However, I think that's the wrong question to ask for a stable branch.
Postgres did export this function in previous versions. Removing it
altogether constitutes an API change and makes extensions that link to
it fail to even load, which is a bad way to fail after a patch version
upgrade. Even if its original use was not sound in the first place.
Ofc my proposed patch is not meant for master, only for stable branches.
Best Regards
Markus
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2022-06-23 20:06:21 | making relfilenodes 56 bits |
| Previous Message | Justin Pryzby | 2022-06-23 19:31:26 | Re: CI and test improvements |