pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Juan Miguel <juanmime@ono.com>
To: Hadley Willan <hadley.willan@deeperdesign.co.nz>
Cc: Gregory S. Williamson <gsw@globexplorer.com>
Cc: PGSQL Admin <pgsql-admin@postgresql.org>
Subject: Re: Forcing connections closed
Date: Thu, 29 Jan 2004 23:36:18 +0100
Message-ID: <40198AE2.5000808@ono.com> (raw)
In-Reply-To: <1075411554.23417.13.camel@atlas.sol.deeper.co.nz>
References: <71E37EF6B7DCC1499CEA0316A25683280105762A@loki.wc.globexplorer.net>
	<1075411554.23417.13.camel@atlas.sol.deeper.co.nz>

You can kill the procs (connections) using kill -9 PID

For example,

ps aux | grep post

gives you a list of the postgres processes (all the active connections, 
and main postmaster). Here you can see the IP of the manchines connected 
from.
Therefore, its easy to create an shell script for killing the connection 
of a client machine.

>Thanks for that, however that's quite heavy handed in that it will stop
>the postgres instance.
>
>Is there any way to close connections to a database without stopping
>postgres itself? 
>
>E.G I have three databases, A,B and C, and only want to close C.
>
>Thanks
>
>On Fri, 2004-01-30 at 10:21, Gregory S. Williamson wrote:
>
>  
>
>>pg_ctl stop    [-W] [-D DATADIR] [-s] [-m SHUTDOWN-MODE]
>>
>>e.g. 
>>
>>pg_ctl stop -D /data/postgres/gex_runtime -m fast
>>
>>will shut down all connections and stop the postgres instance:
>>Shutdown modes are:
>>  smart       quit after all clients have disconnected
>>  fast        quit directly, with proper shutdown
>>  immediate   quit without complete shutdown; will lead to recovery on restart
>>
>>HTH,
>>
>>Greg Williamson
>>DBA
>>GlobeXplorer LLC
>>
>>-----Original Message-----
>>From:	Hadley Willan [mailto:hadley.willan@deeperdesign.co.nz]
>>Sent:	Thu 1/29/2004 1:03 PM
>>To:	PGSQL Admin
>>Cc:	
>>Subject:	[ADMIN] Forcing connections closed
>>
>>Hello,
>>    How do I force postmaster to terminate active connections on other
>>databases?
>>
>>Thanks
>>    
>>
>
>  
>





view thread (9+ messages)  latest in thread

Message-ID: <40198AE2.5000808@ono.com>
Permalink:  ../40198AE2.5000808@ono.com/
Also on:    postgresql.org/message-id/40198AE2.5000808@ono.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: juanmime@ono.com, hadley.willan@deeperdesign.co.nz, gsw@globexplorer.com
  Subject: Re: Forcing connections closed
  In-Reply-To: <40198AE2.5000808@ono.com>
  References: <71E37EF6B7DCC1499CEA0316A25683280105762A@loki.wc.globexplorer.net> <1075411554.23417.13.camel@atlas.sol.deeper.co.nz> <40198AE2.5000808@ono.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox