pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Ryan Chambers <ryan@squaretrade.com>
To: PGSQL Admin <pgsql-admin@postgresql.org>
Subject: Re: Forcing connections closed
Date: Thu, 29 Jan 2004 13:48:22 -0800
Message-ID: <40197FA6.5040508@squaretrade.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>

It's possible to get process ids for clients using something like ps -ef 
| grep postgres. I wonder, is it safe to use kill to terminate those 
threads? If this doesn't mess up the database, it might work.

Hadley Willan wrote:

> 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/
>>
> -- 
> *Hadley Willan* *»* Director *»* _hadley.willan@deeperdesign.com_ 
> <mailto:hadley.willan@deeperdesign.com> *»* +64(21) 28 41 463 Deeper 
> Design Limited *»* +64(7) 377 3328 *»* _www.deeperdesign.com_ 
> <http://www.deeperdesign.com;
>
>
>  
>

view thread (9+ messages)  latest in thread

Message-ID: <40197FA6.5040508@squaretrade.com>
Permalink:  ../40197FA6.5040508@squaretrade.com/
Also on:    postgresql.org/message-id/40197FA6.5040508@squaretrade.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: ryan@squaretrade.com
  Subject: Re: Forcing connections closed
  In-Reply-To: <40197FA6.5040508@squaretrade.com>
  References: <71E37EF6B7DCC1499CEA0316A25683280105762A@loki.wc.globexplorer.net> <1075411554.23417.13.camel@atlas.sol.deeper.co.nz> <40197FA6.5040508@squaretrade.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