Horton

Re: obsoleting plpython2u and defaulting plpythonu to plpython3u

Robert Haas <robertmhaas@gmail.com>

View thread View on postgr.es
From: Robert Haas <robertmhaas@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>, Pavel Raiskup <praiskup@redhat.com>, PostgreSQL Hacker <pgsql-hackers@postgresql.org>
Date: 2018-04-27T14:50:35Z
Lists: pgsql-hackers 
On Thu, Apr 26, 2018 at 4:39 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> I'm not very sure how many moving parts would be involved in making that
> happen.  One thing we should probably do first is retire the pg_pltemplate
> system catalog in favor of making PL extension scripts self-contained,
> as you'd mentioned recently would be a good project to finish off.

Incidentally, it recently came to my notice that we're still issuing
hints that say:

Use CREATE LANGUAGE to load the language into the database.

That is now, and has been for some time, the wrong advice.  We should
really be recommending CREATE EXTENSION.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

Commits

  1. Adjust hints and docs to suggest CREATE EXTENSION not CREATE LANGUAGE.