On Thu, Jun 7, 2012 at 8:44 AM, Robert Haas wrote:
> On Wed, Jun 6, 2012 at 5:21 PM, Tom Lane wrote:
>> Robert Haas writes:
>>> rhaas=# create table pg_catalog.tom (a int);
>>> ERROR: permission denied to create "pg_catalog.tom"
>>
>>> The offending error check is in heap_create(), and based on
On Wed, Jun 6, 2012 at 5:21 PM, Tom Lane wrote:
> Robert Haas writes:
>> rhaas=# create table pg_catalog.tom (a int);
>> ERROR: permission denied to create "pg_catalog.tom"
>
>> The offending error check is in heap_create(), and based on what
>> you're saying here it seems like we should just ri
Robert Haas writes:
> rhaas=# create table pg_catalog.tom (a int);
> ERROR: permission denied to create "pg_catalog.tom"
> The offending error check is in heap_create(), and based on what
> you're saying here it seems like we should just rip it out.
Hmm. Yeah, it seems like the regular permiss
On Wed, Jun 6, 2012 at 4:39 PM, Tom Lane wrote:
> Robert Haas writes:
>> Right now, you can't directly create a relation (table, index,
>> composite type) in the pg_catalog schema, but you can create a
>> non-relation (function, domain, etc.) in the pg_catalog schema.
>
> Surely this is true only
Robert Haas writes:
> Right now, you can't directly create a relation (table, index,
> composite type) in the pg_catalog schema, but you can create a
> non-relation (function, domain, etc.) in the pg_catalog schema.
Surely this is true only for superusers. Superusers can do whatever
they want an
Right now, you can't directly create a relation (table, index,
composite type) in the pg_catalog schema, but you can create a
non-relation (function, domain, etc.) in the pg_catalog schema.
Furthermore, you can create a table in some other schema and then move
it into the pg_catalog schema using AL
