Skip site navigation (1) Skip section navigation (2)

Re: Forcing connections closed

From: Ryan Chambers <ryan(at)squaretrade(dot)com>
To: PGSQL Admin <pgsql-admin(at)postgresql(dot)org>
Subject: Re: Forcing connections closed
Date: 2004-01-29 21:48:22
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-admin
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]
>>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
>>Greg Williamson
>>GlobeXplorer LLC
>>-----Original Message-----
>>From:	Hadley Willan [mailto:hadley(dot)willan(at)deeperdesign(dot)co(dot)nz]
>>Sent:	Thu 1/29/2004 1:03 PM
>>To:	PGSQL Admin
>>Subject:	[ADMIN] Forcing connections closed
>>    How do I force postmaster to terminate active connections on other
> -- 
> *Hadley Willan* *»* Director *»* _hadley(dot)willan(at)deeperdesign(dot)com_ 
> <mailto:hadley(dot)willan(at)deeperdesign(dot)com> *»* +64(21) 28 41 463 Deeper 
> Design Limited *»* +64(7) 377 3328 *»* _www.deeperdesign.com_ 
> <>

In response to

pgsql-admin by date

Next:From: Juan MiguelDate: 2004-01-29 22:36:18
Subject: Re: Forcing connections closed
Previous:From: Hadley WillanDate: 2004-01-29 21:25:54
Subject: Re: Forcing connections closed

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group