Re: erroneous restore into pg_catalog schema - Mailing list pgsql-hackers

From Robert Haas
Subject Re: erroneous restore into pg_catalog schema
Date
Msg-id CA+TgmoYFwF9fPoj+iVNYKBUuqf66Duio_cNtB7qrgSJwxdixCw@mail.gmail.com
Whole thread Raw
In response to Re: erroneous restore into pg_catalog schema  (Andres Freund <andres@2ndquadrant.com>)
Responses Re: erroneous restore into pg_catalog schema  (Andres Freund <andres@2ndquadrant.com>)
Re: erroneous restore into pg_catalog schema  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Mon, May 13, 2013 at 1:03 PM, Andres Freund <andres@2ndquadrant.com> wrote:
>> It disallowed it only for tables, and not for any other object type.
>> I found that completely arbitrary.  It's perfectly obvious that people
>> want to be able to create objects in pg_catalog; shall we adopt a rule
>> that you can put extension there, as long as those extensions don't
>> happen to contain tables?  That is certainly confusing and arbitrary.
>
> Why don't we just prohibit deletion/modification for anything below
> FirstNormalObjectId instead of using the schema as a restriction? Then
> we can allow creation for tables as well.

We currently do, but that led to problems with $SUBJECT.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: erroneous restore into pg_catalog schema
Next
From: Andres Freund
Date:
Subject: Re: erroneous restore into pg_catalog schema