Two vaguely helpful comments: 1. Sometimes this has happened to me when I unknowingly have two terminal psql processes running on the same machine that I'm using to connect to the server. Everyone but yourself may be off the database, but there may be two instances of yourself. :) 2. I've dealt with the situation of how to kick all users off the system by making the client software I write listen for a "disconnect from the database now, dammit" NOTIFY (e.g. 'NOTIFY shutdown_foo_db') and I have the client quit immediately upon receiving this notification the next time they make a query. It's a crude kludge, but usually after 5-10 minutes, everyone's off and I don't have to restart/reload anything. -- Ilan On Sep 20, 2007, at 4:03 PM, Sysadmin wrote:
Ilan Volow "Implicit code is inherently evil, and here's the reason why:" |