Re: [HACKERS] Contrib Schemas

2006-01-13 Thread Simon Riggs
On Thu, 2006-01-12 at 19:33 -0500, Tom Lane wrote: David Fetter [EMAIL PROTECTED] writes: What do you think? I think it's not broken and doesn't need fixing. I have not seen any groundswell of demand for moving the contrib stuff out of the public schema. On the other hand, doing so

Re: [HACKERS] Contrib Schemas

2006-01-13 Thread Josh Berkus
John, Would it be reasonable for there to be a way for the super user to grant access to load approved modules and/or C language functions? I can't see a way to do this except individually, in which case the superuser might as well load the functions. We *have* to be restrictive about this

Re: [HACKERS] Contrib Schemas

2006-01-13 Thread John DeSoi
Hi Josh, On Jan 13, 2006, at 2:34 PM, Josh Berkus wrote: I can't see a way to do this except individually, in which case the superuser might as well load the functions. We *have* to be restrictive about this because a C function can do anything, including overwriting whatever parts of the

Re: [HACKERS] Contrib Schemas

2006-01-12 Thread Mark Kirkwood
David Fetter wrote: Folks, I'm picturing something like this: make install # Option 0 Leave as-is make install --auto_schema [--generate_path_mod] # Option 1 make install --schema=contrib # Option 2 make install --schema=foo

Re: [HACKERS] Contrib Schemas

2006-01-12 Thread Andrew Dunstan
David Fetter said: I'm picturing something like this: make install # Option 0 Leave as-is make install --auto_schema [--generate_path_mod] # Option 1 make install --schema=contrib # Option 2 make install --schema=foo

Re: [HACKERS] Contrib Schemas

2006-01-12 Thread Tom Lane
David Fetter [EMAIL PROTECTED] writes: What do you think? I think it's not broken and doesn't need fixing. I have not seen any groundswell of demand for moving the contrib stuff out of the public schema. On the other hand, doing so *will* break many if not all existing applications that use

Re: [HACKERS] Contrib Schemas

2006-01-12 Thread Josh Berkus
Tom, People who want the contrib stuff segregated can easily make it happen by modifying the contrib .sql files before they run them. The .sql files already have a skeleton for this, eg -- Adjust this setting to control where the objects get created. SET search_path = public; I

[HACKERS] Contrib Schemas

2006-01-12 Thread David Fetter
Folks, For the same reason they feel that *n*x installs shouldn't be messing around in /usr/local, some people also feel that contrib modules shouldn't install in the public schema by default. Before I go a-patching, I'd like to see what people think about how to handle this. A few of

Re: [HACKERS] Contrib Schemas

2006-01-12 Thread Christopher Kings-Lynne
Default schema really has to be public to help the newbies out there. All contribs should come with some sort of standard uninstall.sql script though. Chris Mark Kirkwood wrote: David Fetter wrote: Folks, I'm picturing something like this: make install

Re: [HACKERS] Contrib Schemas

2006-01-12 Thread John DeSoi
On Jan 12, 2006, at 9:03 PM, Christopher Kings-Lynne wrote: Default schema really has to be public to help the newbies out there. All contribs should come with some sort of standard uninstall.sql script though. Speaking of contrib newbies and install/uninstall, I recently had the need