Re: fix crash with Python 3.11 - Mailing list pgsql-hackers

From Markus Wanner
Subject Re: fix crash with Python 3.11
Date
Msg-id a63db964-196b-f025-40f3-658b8c8da78b@enterprisedb.com
Whole thread Raw
In response to Re: fix crash with Python 3.11  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: fix crash with Python 3.11  (Tom Lane <tgl@sss.pgh.pa.us>)
List 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



pgsql-hackers by date:

Previous
From: Justin Pryzby
Date:
Subject: Re: CI and test improvements
Next
From: Robert Haas
Date:
Subject: making relfilenodes 56 bits