From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
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 14:50:35 |
Message-ID: | CA+TgmoaJTUDMSuSCg4k08Dv8vhbrJq9nP3ZfPbmysVz_616qxw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Apr 26, 2018 at 4:39 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2018-04-27 14:52:32 | Re: Built-in connection pooling |
Previous Message | Merlin Moncure | 2018-04-27 13:49:52 | Re: Built-in connection pooling |