From: | KÖPFERL Robert <robert(dot)koepferl(at)sonorys(dot)at> |
---|---|
To: | |
Cc: | pgadmin-support(at)postgresql(dot)org |
Subject: | Wish for an option to close a DB |
Date: | 2005-01-18 16:45:02 |
Message-ID: | ED4E30DD9C43D5118DFB00508BBBA76EB16568@neptun.sonorys.at |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-support |
Hi,
we've got often the problem that we were working on a database just to drop
it afrerwarts and recreate it from the current developement schema. However
postgres denies to drop a DB until all sessions are closed. Since we were
working on it and pgAdmin has no db-specific option (or did we just oversee
it) to close a specific DB, we have to close the whole connection. This is
bad.
I whish myself an option in the context menu to detach a db.
And BUG: If I was working on a table or stored procedure, the dialog is
still open and I close down the connection, pgAdmin does this. The dialogs
still remain. After an event, reconnected or not, PgAdmin crashes (Jan 14
on w2k).
PS. Noone is using the mentioned DB as login DB
From | Date | Subject | |
---|---|---|---|
Next Message | Alexander Borkowski | 2005-01-18 22:41:55 | Re: Wish for an option to close a DB |
Previous Message | KÖPFERL Robert | 2005-01-17 10:15:45 | Re: New Operator broken |