Re: Cannot create a type in pg_catalog

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Cc: Dave Page <dpage(at)postgresql(dot)org>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: Cannot create a type in pg_catalog
Date: 2007-08-23 14:40:01
Message-ID: 1504.1187880001@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> Dave Page wrote:
>> - "are currently disallowed" implies that sometimes it is allowed. How
>> does one control that, or is it implying something that is not the case,
>> or only the case in unusual circumstances such as a standalone backend?

> It is allowed in standalone mode AFAIR (maybe when specifying a flag
> like -P or -O).

Yeah, you need one of those switches, I can never remember which is
which without looking.

The actual prohibition is on inserting a new pg_class row, which Dave's
command is trying to do because he's trying to create a composite type.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Dave Page 2007-08-23 14:57:43 Re: Cannot create a type in pg_catalog
Previous Message Alvaro Herrera 2007-08-23 14:34:49 Re: Cannot create a type in pg_catalog