The users are accessing the database using PhpPgAdmin. I thought that
this might happen if they closed the browser without closing logging
off. I know that if you do that the browser will return to where you
left it, when you open it again. I tried that with my own database,
and I couldn't reproduce the condition.
Carol
On Mar 2, 2009, at 8:31 PM, Tom Lane wrote:
> Carol Walter <walterc@indiana.edu> 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@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-admin