Re: Possible bug with ALTER LANGUAGE ... OWNER TO ... - Mailing list pgsql-general

From Alvaro Herrera
Subject Re: Possible bug with ALTER LANGUAGE ... OWNER TO ...
Date
Msg-id 20081209234045.GQ4053@alvh.no-ip.org
Whole thread Raw
In response to Re: Possible bug with ALTER LANGUAGE ... OWNER TO ...  (Erik Jones <ejones@engineyard.com>)
Responses Re: Possible bug with ALTER LANGUAGE ... OWNER TO ...
List pgsql-general
Erik Jones wrote:
>
> On Dec 8, 2008, at 1:42 PM, Tom Lane wrote:
>
>> Erik Jones <ejones@engineyard.com> writes:
>>> I've just run up against a problem with ALTER LANGUAGE ... OWNER
>>> TO ... wherein the change of ownership does not propagate to a
>>> language's handler and validator functions preventing you from
>>> dropping the role if it created a language.  I'm assuming a valid
>>> workaround is manually change the owner of the handler and validator
>>> functions but I'd think that changing a languages owning role should
>>> propagate to any other objects created when the language was created.
>>
>> Why?  The underlying functions are independent objects, in the general
>> case.
>
> While I understand what you're saying, in the general case, in this
> specific case I have a hard time grokking it.  I guess I was thinking in
> terms of a language owning it's handler and validator functions but I now
> see that dropping a language doesn't also drop the underlying functions,
> which I also find unintuitive.

Well, since CREATE LANGUAGE creates the functions internally, it does
make a certain amount of sense that the functions are also handled
internally when you do stuff to the language.

--
Alvaro Herrera                                http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.

pgsql-general by date:

Previous
From: "Scott Marlowe"
Date:
Subject: Re: unstable SELECT performance under load
Next
From: Tom Lane
Date:
Subject: Re: Possible bug with ALTER LANGUAGE ... OWNER TO ...