Re: Renaming schema's [SOLVED]

Tom Lane wrote:
> Jochem van Dieten <jochemd(at)oli(dot)tudelft(dot)nl> writes:
>
>>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.

I asked on the pgadmin-support list and Dave Page answered:
<quote>
pgAdmin hides system objects by default, but in the case of the public
schema it makes an exception bcause hiding public would not be sensible.
It does it by a combination of name and OID: the oid is less than the
last system oid, so it is hidden, except if it is called public.

Switch on show System Objects on the view menu and you should see it.
</quote>

Switching on System Objects indeed makes the renamed schema visible in
pgAdminII.

Jochem