Re: language handlers in public schema?

On 2005-06-24, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
>> Is there any reason for us to keep putting the language handler
>> functions in the public schema?
>
> I believe one of the issues there is that pg_dump doesn't dump functions
> that are in pg_catalog. You could possibly fix it to make an exception
> for functions that are referenced by pg_language entries, but I think
> this would be a nontrivial change.

I think there's a case for a schema to exist by default that (a) does not
have public CREATE rights and (b) is not the default place to create
objects. There might even be a case for two of them: one on the default
search path and one not. Then stuff like languages, small contrib modules
(large ones should create their own schema), etc., can all default to
installing somewhere other than public.

--
Andrew, Supernews
http://www.supernews.com - individual and corporate NNTP services