Re: erroneous restore into pg_catalog schema

From: Greg Stark <stark(at)mit(dot)edu>
To: Stephen Frost <sfrost(at)snowman(dot)net>
Cc: Dimitri Fontaine <dimitri(at)2ndquadrant(dot)fr>, Marko Kreen <markokr(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Erik Rijkers <er(at)xs4all(dot)nl>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, Kohei KaiGai <kaigai(at)kaigai(dot)gr(dot)jp>
Subject: Re: erroneous restore into pg_catalog schema
Date: 2013-06-10 14:02:22
Message-ID: CAM-w4HMDRGEp46wvCDQRXLwPE5kRZ1W4AdhLg+YLg8FsuKkAbw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Jun 10, 2013 at 2:03 PM, Stephen Frost <sfrost(at)snowman(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message MauMau 2013-06-10 14:02:59 Re: Hard limit on WAL space used (because PANIC sucks)
Previous Message Dimitri Fontaine 2013-06-10 13:35:27 Re: erroneous restore into pg_catalog schema