Re: obsoleting plpython2u and defaulting plpythonu to plpython3u

Tom Lane <tgl@sss.pgh.pa.us>

From: Tom Lane <tgl@sss.pgh.pa.us>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>, Pavel Raiskup <praiskup@redhat.com>, PostgreSQL Hacker <pgsql-hackers@postgresql.org>
Date: 2018-04-27T15:44:52Z
Lists: pgsql-hackers
Robert Haas <robertmhaas@gmail.com> writes:
> 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.

Right.  It's too late in the v11 cycle to consider any of this other work
right now, but I think it'd be reasonable to adjust those message(s) for
v11 ... any objections?  I see two places in functioncmds.c that ought
to change, as well as a few examples in the SGML docs.

			regards, tom lane


Commits

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