| From: | Carlos Mennens <carlos(dot)mennens(at)gmail(dot)com> |
|---|---|
| To: | PostgreSQL <pgsql-general(at)postgresql(dot)org> |
| Subject: | How To Handle Hung Connections |
| Date: | 2011-12-20 15:50:57 |
| Message-ID: | CAAQLLO7TaifOdudiX8J6zBMrNcGcTA+6VdB6Z3YzLRX8L=ffrQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
I'm attempting to delete a database that I've obviously not closed
connections from cleanly.
postgres=# DROP DATABASE filters;
ERROR: database "filters" is being accessed by other users
DETAIL: There are 4 other session(s) using the database.
How exactly would one manage this issue from a PostgreSQL
administration stand point? I know there are not real users connected
to this database but rather zombie connections. Is there a way to
force the DROP command or can I manually view / kill connections to
this database w/o having to restart the entire PostgreSQL daemon and
impact other active databases?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mike Blackwell | 2011-12-20 16:06:44 | Re: How To Handle Hung Connections |
| Previous Message | Adrian Klaver | 2011-12-20 15:10:13 | Re: pg_restore should restore the schema comments and the database properties |