From: | Andreas Pflug <pgadmin(at)pse-consulting(dot)de> |
---|---|
To: | KÖPFERL Robert <robert(dot)koepferl(at)sonorys(dot)at> |
Cc: | pgadmin-support(at)postgresql(dot)org |
Subject: | Re: Wish for an option to close a DB |
Date: | 2005-01-28 13:54:56 |
Message-ID: | 41FA4430.7000909@pse-consulting.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-support |
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
From | Date | Subject | |
---|---|---|---|
Next Message | Andreas Pflug | 2005-01-28 14:06:52 | Re: Segmentation fault |
Previous Message | Vasilev Max | 2005-01-28 13:51:29 | Re: Trouble with pgadmin installation |