From: | Jochem van Dieten <jochemd(at)oli(dot)tudelft(dot)nl> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Renaming schema's |
Date: | 2002-12-02 01:04:49 |
Message-ID: | 3DEAB1B1.10306@oli.tudelft.nl |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Tom Lane wrote:
> Jochem van Dieten <jochemd(at)oli(dot)tudelft(dot)nl> writes:
>
>>I have tried to rename a schema using:
>>test=# update pg_catalog.pg_namespace
>>test-# set nspname = 'jochemd'
>>test-# where nspname = 'public';
>
>
>>This didn't work out very well, the schema became invisible in
>>pgAdminII, something I wouldn't want to do to our customers.
>
> I would expect that to work; perhaps the problem is pgAdminII's?
After looking at some more databases it turned out that the public
schema always has OID 2200. 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).
So the question becomes if OID 2200 is reserved or hardcoded in the
backend for the public schema or if this assumption from pgAdminII is
incorrect?
Jochem
From | Date | Subject | |
---|---|---|---|
Next Message | Grand Titus | 2002-12-02 01:11:26 | Re: how to make an 'UNLOCK'? |
Previous Message | Tom Lane | 2002-12-02 00:34:03 | Re: Renaming schema's |