That's interesting and is probably the answer to my question as to why
this happens. Thanks, Nick. What it doesn't explain is why I was
able to connect to a test database using PhpPgAdmin and close the
browser, without logging out, and I was able to rename my test
database. I couldn't reproduce the behavior. I wonder if it is a
property of the particular browser or desktop platform. I was using
Firefox on a Mac. The users use Windows. I'm not sure which browser
they are using.
I also still want to know if there is a way to gracefully break that
persistent connection on the server side. Using a PHP front end over
the web, I don't always know who has a browser open.
Thanks,
Carol
On Mar 4, 2009, at 9:36 AM, Hajek, Nick wrote:
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
A persistent connection is often used with PHP. With this, PHP will
maintain the connection after a browser is closed or a user is logged
off so that the next time a db connection is required, the response
time
is better. To break any persistent connections would require
restarting
the browser.
Nick Hajek
--
Sent via pgsql-admin mailing list (pgsql-admin@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
