Tom Lane wrote:
> Bruce Momjian <pgman@candle.pha.pa.us> writes:
> > Tom Lane wrote:
> >> The behavior that I think would be most useful would be to automatically
> >> transpose CREATE FUNCTION ... LANGUAGE "plpython" into CREATE FUNCTION
> >> ... LANGUAGE "plpythonu". Which we could do with an ugly hack in CREATE
> >> FUNCTION (ugly, but no worse than things we've done to index opclass
> >> names, for example). But it could be too confusing.
>
> > You mean in gram.y? Yes, I think that is our only choice.
>
> Actually I think it should be in functioncmds.c. I moved the special
> kluges for opclass names out of gram.y and into indexcmds.c awhile ago.
> But that's just an implementation detail --- we really need to still be
> thinking about whether this is the behavior we want or not. Someone
> else made a fair point that such a kluge might not actually make life
> any easier for reloading dump files. If we do it that way, then if a
> non-superuser tries to CREATE FUNCTION ... LANGUAGE "plpython" it will
> fail (not being trusted) and so he's got no hope of loading the dump
> without editing anyway. If that's true, there's not much point in
> introducing a hidden kluge.
Well, it does fix the super-user case, so we have to tell non-super
users to get their administrator to install it, which actually is the
right solution anyway for non-super-user installs of plpython language
modules anyway.
--
Bruce Momjian | http://candle.pha.pa.us
pgman@candle.pha.pa.us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
