Re: obsoleting plpython2u and defaulting plpythonu to plpython3u - Mailing list pgsql-hackers

From Tom Lane
Subject Re: obsoleting plpython2u and defaulting plpythonu to plpython3u
Date
Msg-id 27457.1524843892@sss.pgh.pa.us
Whole thread Raw
In response to Re: obsoleting plpython2u and defaulting plpythonu to plpython3u  (Robert Haas <robertmhaas@gmail.com>)
List 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


pgsql-hackers by date:

Previous
From: Chapman Flack
Date:
Subject: Re: Add read-only param to set_config(...) / SET that effects (atleast) customized runtime options
Next
From: Tom Lane
Date:
Subject: Re: obsoleting plpython2u and defaulting plpythonu to plpython3u