From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, Pavel Raiskup <praiskup(at)redhat(dot)com>, PostgreSQL Hacker <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: obsoleting plpython2u and defaulting plpythonu to plpython3u |
Date: | 2018-04-27 15:44:52 |
Message-ID: | 27457.1524843892@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Robert Haas <robertmhaas(at)gmail(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2018-04-27 15:51:57 | Re: obsoleting plpython2u and defaulting plpythonu to plpython3u |
Previous Message | Chapman Flack | 2018-04-27 15:42:00 | Re: Add read-only param to set_config(...) / SET that effects (at least) customized runtime options |