From: | Heikki Linnakangas <heikki(at)enterprisedb(dot)com> |
---|---|
To: | Norbert Radyk <fragiel(at)wp(dot)pl> |
Cc: | pgsql-jdbc(at)postgresql(dot)org |
Subject: | Re: Closing all existing PostgreSQL database connections |
Date: | 2007-05-07 10:32:04 |
Message-ID: | 463F0024.2060701@enterprisedb.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
Norbert Radyk wrote:
> I've got a question about PostgreSQL JDBC API. Is there any way to
> close all existing & open connections to the particular database. I
> mean the connections made by some external programs too.
>
> I simply need to drop the database to which there are some open
> external connections. I cannot get the java.sql.Connection object in
> order to close the connection, but maybe there is some other way to do
> this?
Unfortunately there's no supported way to terminate individual backends.
From command line, you can use "kill" to do that, but it's not a very
well-tested codepath and it's not officially supported. IOW, not
recommended on production servers.
There's also a tool called "cutter", which let's you terminate any
TCP/IP connection: http://www.lowth.com/cutter/. I've never used that
myself, but it seems like a safe option.
The easiest option is to just restart postmaster.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Cramer | 2007-05-07 10:47:23 | Re: Problem with Utilizing executeBatch() with stored procedures |
Previous Message | Kranti Parisa | 2007-05-07 07:56:26 | Problem with Utilizing executeBatch() with stored procedures |