Thread: Wish for an option to close a DB

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

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

Thanks, I'll remember it and have a try.

> -----Original Message-----
> From: Alexander Borkowski [mailto:alexander.borkowski@abri.une.edu.au]
> Sent: Dienstag, 18. Jänner 2005 23:42
> To: KÖPFERL Robert
> Cc: pgadmin-support
> Subject: Re: [pgadmin-support] Wish for an option to close a DB
>
>
> 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
>

KÖPFERL Robert wrote:
> 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).

Yes, don't do that. This is a strong argument *not* to implement db 
disconnection, I'd expect even more frequent crashes.

Currently, we don't track which property dialog is open and using a 
specific connection. I've put that on TODO.txt.

Regards,
Andreas