Horton

Re: erroneous restore into pg_catalog schema

Greg Stark <stark@mit.edu>

View thread View on postgr.es
From: Greg Stark <stark@mit.edu>
To: Stephen Frost <sfrost@snowman.net>
Cc: Dimitri Fontaine <dimitri@2ndquadrant.fr>, Marko Kreen <markokr@gmail.com>, Tom Lane <tgl@sss.pgh.pa.us>, Robert Haas <robertmhaas@gmail.com>, Alvaro Herrera <alvherre@2ndquadrant.com>, Erik Rijkers <er@xs4all.nl>, "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>, Kohei KaiGai <kaigai@kaigai.gr.jp>
Date: 2013-06-10T14:02:22Z
Lists: pgsql-hackers 
On Mon, Jun 10, 2013 at 2:03 PM, Stephen Frost <sfrost@snowman.net> wrote:
> Having a schema that isn't pg_catalog doesn't necessairly mean we need a
> schema per extension.  Just a 'pg_extensions' schema, which is added to
> search_path behind the scenes (just like pg_catalog..) would be better
> than having everything go into pg_catalog.

Well no objection here. That's just like having /usr/local/{lib,bin,etc}.

> I'd prefer that we let the
> admins control both where extensions get installed to and what schemas
> are added to the end of the search_path.

This I object to. That's like having /usr/local/{apache,pgsql,kde,gnome}/bin.




-- 
greg

Commits

  1. Extend and improve use of EXTRA_REGRESS_OPTS.

  2. Remove misplaced sanity check from heap_create().

  3. Silently ignore any nonexistent schemas that are listed in search_path.