This has happened or is happening to me again, only this time, it's a
database that I just created. I restored another database into a test
database. One of the tables is empty. I want to drop the test
database and create a new one. When I try to drop the test database,
I get this error -
template1=# drop database km_tezt;
ERROR: database "km_tezt" is being accessed by other users
template1=# select * from pg_prepared_xacts;
transaction | gid | prepared | owner | database
-------------+-----+----------+-------+----------
(0 rows)
This database is one that I created just a few hours ago just to test
some things myself. There can be no one in it except me. I
completely closed out of the database, closed out of the system, and
closed my terminal session. Still I get the error. This time the
database has not been accessed through PHP at all.
Carol
On Mar 2, 2009, at 8:31 PM, Tom Lane wrote:
Carol Walter <walterc@xxxxxxxxxxx> writes:
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.
Hmph. Are you sure nothing was connected? One thing that frequently
trips people up here is uncommitted prepared transactions --- look in
pg_prepared_xacts.
regards, tom lane
--
Sent via pgsql-admin mailing list (pgsql-admin@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
--
Sent via pgsql-admin mailing list (pgsql-admin@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
