| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | Hannu Krosing <hannu(at)2ndquadrant(dot)com>, PostgreSQL-development Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: putting plproxy in pg_pltemplate |
| Date: | 2010-07-16 16:49:25 |
| Message-ID: | 17817.1279298965@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> On fre, 2010-07-16 at 14:13 +0300, Hannu Krosing wrote:
>> Should we put some externally managed languages , like pl/proxy also in
>> pgtemplate, so that CREATE LANGUAGE would work on them ?
> This has been rejected several times before. See:
> http://archives.postgresql.org/pgsql-hackers/2009-01/msg00050.php
Note that there's nothing stopping a DBA from putting new entries in
pg_pltemplate within his installation. Peter's points are valid reasons
why we should be wary of putting entries into our distribution --- it's
hard to control this sort of stuff over the timescale of a PG major
release. But per-installation it doesn't seem unreasonable.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Chris Browne | 2010-07-16 16:51:18 | Re: SHOW TABLES |
| Previous Message | Brendan Jurd | 2010-07-16 16:47:23 | Re: patch: to_string, to_array functions |