| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Markus Wanner <markus(dot)wanner(at)enterprisedb(dot)com> |
| 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 22:54:43 |
| Message-ID: | 134011.1656024883@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Markus Wanner <markus(dot)wanner(at)enterprisedb(dot)com> writes:
> 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.
Does such code exist? I don't see any other calls in Debian code search,
and I find it hard to believe that anyone would think such a thing is
maintainable.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bagga, Rishu | 2022-06-24 00:39:41 | Re: SLRUs in the main buffer pool - Page Header definitions |
| Previous Message | Tom Lane | 2022-06-23 22:43:40 | Re: NAMEDATALEN increase because of non-latin languages |