Re: language handlers in public schema? - Mailing list pgsql-hackers

From Andrew - Supernews
Subject Re: language handlers in public schema?
Date
Msg-id slrndbmpcd.192v.andrew+nonews@trinity.supernews.net
Whole thread Raw
In response to language handlers in public schema?  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
On 2005-06-24, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Andrew Dunstan <andrew@dunslane.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


pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: language handlers in public schema?
Next
From: Bruce Momjian
Date:
Subject: Re: [PATCHES] O_DIRECT for WAL writes