Rightly as Guillaume said, tampering with a system table isn't a very good idea.
This is what he suggested:
1. Lets say you are connected to Database A
2. Reconnect to Database B on the server (this database B could be any database other than A on the server)
3. Rename database A to C
4. Reconnect to C
Without step 2, step 3 would always spew the error about unable to rename the 'current database'.
Robins
---------- Forwarded message ----------
From: Mag Gam <magawake@xxxxxxxxx>
Date: Feb 7, 2008 9:22 AM
Subject: Re: rename database
To: Guillaume Lelarge <guillaume@xxxxxxxxxxxx>
Cc: Nuwan Liyanage <alnuwan2@xxxxxxxxx>, pgsql-admin@xxxxxxxxxxxxxx
what's the right way to rename a database then?
From: Mag Gam <magawake@xxxxxxxxx>
Date: Feb 7, 2008 9:22 AM
Subject: Re: rename database
To: Guillaume Lelarge <guillaume@xxxxxxxxxxxx>
Cc: Nuwan Liyanage <alnuwan2@xxxxxxxxx>, pgsql-admin@xxxxxxxxxxxxxx
what's the right way to rename a database then?
On Feb 6, 2008 5:33 PM, Guillaume Lelarge <guillaume@xxxxxxxxxxxx> wrote:
Nuwan Liyanage wrote:A better way is to connect to another database (template1 for exemple,
> Ok I think I got it. I just went ahead and updated the pg_database table
> and it works..
>
but you would better use another one) and fire your statement there.
Updating system table can be dangerous.
--
Guillaume.
http://www.postgresqlfr.org
http://dalibo.com
---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
