Re: Renaming schema's - Mailing list pgsql-general

From Tom Lane
Subject Re: Renaming schema's
Date
Msg-id 3591.1038792197@sss.pgh.pa.us
Whole thread Raw
In response to Re: Renaming schema's  (Jochem van Dieten <jochemd@oli.tudelft.nl>)
Responses Re: Renaming schema's [SOLVED]  (Jochem van Dieten <jochemd@oli.tudelft.nl>)
List pgsql-general
Jochem van Dieten <jochemd@oli.tudelft.nl> writes:
> After looking at some more databases it turned out that the public
> schema always has OID 2200.

That is what it's assigned during initdb.

> I would expect pgAdminII assuming that OID
> 2200 = public schema to be the cause of this problem (I tried messing
> with ACL's to no avail and changing the name of other schema's works).

I think it's a bad idea for it to assume that.  There's no reason,
for example, why one shouldn't be able to drop and later recreate the
public schema.  The public schema isn't magic at all, except that by
convention it's part of the standard search path --- and that's driven
off its name, not its OID.

            regards, tom lane

pgsql-general by date:

Previous
From: Joe Conway
Date:
Subject: Re: Renaming schema's
Next
From: Tom Lane
Date:
Subject: Re: how to make an 'UNLOCK'?