How To Handle Hung Connections - Mailing list pgsql-general

From Carlos Mennens
Subject How To Handle Hung Connections
Date
Msg-id CAAQLLO7TaifOdudiX8J6zBMrNcGcTA+6VdB6Z3YzLRX8L=ffrQ@mail.gmail.com
Whole thread Raw
Responses Re: How To Handle Hung Connections  (Mike Blackwell <mike.blackwell@rrd.com>)
List 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?

pgsql-general by date:

Previous
From: Adrian Klaver
Date:
Subject: Re: pg_restore should restore the schema comments and the database properties
Next
From: Mike Blackwell
Date:
Subject: Re: How To Handle Hung Connections