| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, 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 17:05:35 |
| Message-ID: | 1279299871-sup-3429@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Excerpts from Tom Lane's message of vie jul 16 12:49:25 -0400 2010:
> 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.
Since a week ago, PL/php ships a small install.sql script that adds a
pg_pltemplate entry. This seems easy enough for the DBA.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2010-07-16 17:06:38 | Re: psql auto-completion for multiple where clauses |
| Previous Message | Hitoshi Harada | 2010-07-16 17:03:03 | Re: reducing NUMERIC size for 9.1 |