From: Tom Lane <tgl@sss.pgh.pa.us>
To: Markus Wanner <markus.wanner@enterprisedb.com>
cc: Peter Eisentraut <peter.eisentraut@enterprisedb.com>, exclusion@gmail.com,
        pgsql-hackers@lists.postgresql.org
Subject: Re: fix crash with Python 3.11
In-reply-to: <defd749a-8410-841d-1126-21398686d63d@enterprisedb.com>
References: <3375ffd8-d71c-2565-e348-a597d6e739e3@enterprisedb.com>
 <3890110.1642373624@sss.pgh.pa.us>
 <73daabb7-9fc7-fb7a-5e06-a968c611b032@enterprisedb.com>
 <2255118.1643126084@sss.pgh.pa.us>
 <bd4dd309-c889-c20c-6be8-a3943cd94882@enterprisedb.com>
 <1103370.1644273481@sss.pgh.pa.us> <1216692.1645644682@sss.pgh.pa.us>
 <1533956.1645731245@sss.pgh.pa.us> <3027328.1655829211@sss.pgh.pa.us>
 <defd749a-8410-841d-1126-21398686d63d@enterprisedb.com>
Comments: In-reply-to Markus Wanner <markus.wanner@enterprisedb.com>
	message dated "Thu, 23 Jun 2022 09:41:00 +0200"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <3922715.1655991297.1@sss.pgh.pa.us>
Date: Thu, 23 Jun 2022 09:34:57 -0400
Message-ID: <3922716.1655991297@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/3922716.1655991297%40sss.pgh.pa.us>
Precedence: bulk

Markus Wanner <markus.wanner@enterprisedb.com> writes:
> Actually, the backport of 2e517818f ("Fix SPI's handling of errors") 
> already broke the API for code using SPICleanup, as that function had 
> been removed. Granted, it's not documented, but still exported.

Under what circumstances would it be OK for outside code to call
SPICleanup?

			regards, tom lane