I'm not sure I understand. If there is a lag time between when
someone exits the database and when the database "knows" that no one
is still in it, then that shouldn't be the problem here. I tried a
number of time over the course of 24 hours to rename the database and
it always reported that the database was in use. No one was logged in
but me, but the database still reported that the database was in use.
I was connect to template1 and trying to rename the other database
from there.
Carol
On Mar 2, 2009, at 4:23 PM, Tom Lane wrote:
> Carol Walter <walterc@indiana.edu> writes:
>> Well, most recently I had created a new database using UTF8 encoding
>> and I had restored data to it, that had been in a database using
>> SQL_ASCII. I wanted to rename the original database. When I tried
>> to
>> rename it, I got the message that I couldn't do it because the
>> database was in use. This particular database is in a 8.2.4 release.
>> I'm moving to 8.3.n but I'm not there yet.
>
> OK. Consulting the CVS history, I see that RENAME DATABASE does have
> a delay in it, but only in 8.3.x.
>
> regards, tom lane
>
> --
> Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-admin