From: | Alexander Borkowski <alexander(dot)borkowski(at)abri(dot)une(dot)edu(dot)au> |
---|---|
To: | KÖPFERL Robert <robert(dot)koepferl(at)sonorys(dot)at> |
Cc: | pgadmin-support <pgadmin-support(at)postgresql(dot)org> |
Subject: | Re: Wish for an option to close a DB |
Date: | 2005-01-18 22:41:55 |
Message-ID: | 41ED90B3.1000305@abri.une.edu.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-support |
Hello,
> 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.
I second that wish. Here is what I found useful as a workaround: If you
select the "Databases" item in the treeview and do a refresh (via
hitting F5 or from the context menu item), pgAdmin will close all
connections to that server _except_ for the one connection to the
initial database for that server, i.e. you only have to disconnect if
you drop the database listed as being the one pgAdmin connects to by
default when connecting to this particular server.
Cheers,
Alex
From | Date | Subject | |
---|---|---|---|
Next Message | cathy.hemsley | 2005-01-19 14:08:34 | Pgadmin 3 version 1.2.0 crashes on every connection attempt |
Previous Message | KÖPFERL Robert | 2005-01-18 16:45:02 | Wish for an option to close a DB |