| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
| Subject: | Re: pg_pltemplate entries for external PLs |
| Date: | 2008-12-31 12:00:55 |
| Message-ID: | 200812311400.56417.peter_e@gmx.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wednesday 31 December 2008 05:50:19 Tom Lane wrote:
> That was part of the original concept for pg_pltemplate, but IIRC there
> was push-back from some folks who thought it was a bad idea. I don't
> recall what their arguments were exactly;
Basically, we have no information about what the proper parameters of external
languages would be. (We have some pretty good ideas, but that's not the
same.) Especially if we override the trusted/untrustedness, we could create
complete disaster.
Ultimately, as we add more loadable facilities (languages, plugins/modules,
foreign-data wrappers), we will need a better upgrade mechanism anyway than
maintaining our own override list of everything in the world. So let's just
leave this mechanism restricted to the built-in languages for now.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2008-12-31 12:02:12 | Re: TODO items for window functions |
| Previous Message | Peter Eisentraut | 2008-12-31 11:51:44 | Re: version() output vs. 32/64 bits |