From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | Thomas Hallgren <thhal(at)mailblocks(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Attention PL authors: want to be listed in template table? |
Date: | 2005-09-08 00:24:47 |
Message-ID: | 1570.1126139087@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:
> Extensibility means you don't control the naming. I guess if you want
> to say that this whole idea of extensibility in the language handler
> area is hereby withdrawn, doesn't work, never existed, then let's make
> that clear. Then we can hardcode everything, tell people, if you want
> to write a language handler, you should talk to us so we can arrange
> the hooks. That is the direction we're headed in.
Not at all! The direction we're headed in is that there are two layers
of abstraction instead of only one. What I put forward in my original
proposal was that there would be a superuser-alterable catalog of PL
templates and then pg_language would indicate what's actually available
in a particular database. I do not see that that's noticeably less
flexible than what we have done all along; especially seeing that the
DBA is not required to have a template for any particular PL.
I do concede that you've provided good reasons why a hard-wired template
table is not an adequate stopgap measure. If I go ahead and put in the
originally-proposed system catalog, will you be satisfied?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2005-09-08 00:28:10 | Re: initdb profiles |
Previous Message | Peter Eisentraut | 2005-09-08 00:12:01 | Re: initdb profiles |