Re: erroneous restore into pg_catalog schema

Stephen Frost <sfrost@snowman.net>

From: Stephen Frost <sfrost@snowman.net>
To: Dimitri Fontaine <dimitri@2ndQuadrant.fr>
Cc: Greg Stark <stark@mit.edu>, 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-11T05:14:21Z
Lists: pgsql-hackers
* Dimitri Fontaine (dimitri@2ndQuadrant.fr) wrote:
> Stephen Frost <sfrost@snowman.net> writes:
> > While having one place to put everything sounds great, it doesn't do a
> > whole lot of good if you consider conflicts- either because you want
> > multiple versions available or because there just happens to be some
> > overlap in function names (or similar).  There are also extensions which
> > have more than just functions in them but also tables, which increases
> > the chances of a conflict happening.  Having the extension authors end
> > up having to prefix everything with the name of the extension to avoid
> > conflicts would certainly be worse than actually using schemas.
> 
> Now you're not talking about *default* settings anymore, or are you?

What happens with the default settings when you try to install two
extensions that have overlapping function signatures..?  I can't imagine
it 'just works'..  And then what?  Is there a way that an admin can set
up search paths for individual users which provide the 'right' function
and work even when the user decides to change their search_path?

	Thanks,

		Stephen

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.