plpython: Remove support for major version conflict detection

From: Peter Eisentraut <peter(at)eisentraut(dot)org>
To: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: plpython: Remove support for major version conflict detection
Date: 2025-08-09 17:18:39
Message-ID: 9eb9feb6-1df3-4f0c-a0dc-9bcf35273111@eisentraut.org
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

This essentially reverts commit 866566a690b, which installed safeguards
against loading plpython2 and plpython3 into the same process. We don't
support plpython2 anymore, so this is obsolete.

The Python and PL/Python initialization now happens again in _PG_init()
rather than the first time a PL/Python call handler is invoked. (Often,
these will be very close together.)

I kept the separate PLy_initialize() function introduced by 866566a690b
to keep _PG_init() a bit modular.

(I'm looking at the some further work to allow multiple interpreters in
PL/Python, so I'm trying to clean up the initialization code a bit first.)

Attachment Content-Type Size
0001-plpython-Remove-support-for-major-version-conflict-d.patch text/plain 5.1 KB

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2025-08-09 18:54:11 Re: Making type Datum be 8 bytes everywhere
Previous Message Tom Lane 2025-08-09 16:44:51 Re: Making type Datum be 8 bytes everywhere