Re: obsoleting plpython2u and defaulting plpythonu to plpython3u
Andres Freund <andres@anarazel.de>
From: Andres Freund <andres@anarazel.de>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Pavel Raiskup <praiskup@redhat.com>, Peter Eisentraut <peter.eisentraut@2ndquadrant.com>, PostgreSQL Hacker <pgsql-hackers@postgresql.org>
Date: 2018-04-27T17:28:20Z
Lists: pgsql-hackers
On 2018-04-27 13:19:43 -0400, Tom Lane wrote: > If we agree that something like this is the way to go, I wonder if we > shouldn't squeeze it into v11. If we wait till v12, that's not going > to ship till late 2019, which is going to be getting uncomfortably > close to when PEP 394 might change if we believe Fedora's schedule. I think that'd be reasonable. Another alternative would be to have a 'plpython' extension that depends on plpython2. That'd require users to specify CASCADE when creating it, but that actually seems like it could be a useful hint... I think it's probably not worth going that route though, because reassigning objects from one extension to another is more work than reasonable... Greetings, Andres Freund
Commits
-
Adjust hints and docs to suggest CREATE EXTENSION not CREATE LANGUAGE.
- 2e83e6bd74ee 11.0 landed