From: Brian A. Seklecki <lavalamp@spiritual-machines.org>
To: pgsql-admin@postgresql.org
Subject: SIGKILL and force disconnecting user sessions
Date: Mon, 22 Sep 2008 09:43:29 -0400
Message-ID: <1222091009.3153.84.camel@soundwave.ws.pitbpa0.priv.collaborativefusion.com> (raw)
This one really isn't in the docs, so we'll add it to the Wiki
afterwords, but:
We've got some shared PG instances with more than one production
application (yes, I know this is a bad practice, but virtualization
options are hit and miss).
We need to kill apache P-conn pools from a an application/web server
cluster for a specific database. We use a load-balancer, so we shut
down the HA L4 Service VIP that the web servers pconnect() to, to
prevent new incoming connections.
The problem is then net.inet.tcp.* timeouts. We need to cane existing
connections with a quickness, and pg_stat_activity is a read-only view.
We need to kill the stale pcons, so just:
$ pkill -a [database string]
The connection goes away as "Disconnected per admin command"
I just want to confirm:
1) There are no data consistency threats to SIGKIL a child thread
process? Transactions and locks will be handled gracefully?
2) There are no pgsql/admin level CLI builtin commands to do this in a
more graceful manor?
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 using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: lavalamp@spiritual-machines.org
Subject: Re: SIGKILL and force disconnecting user sessions
In-Reply-To: <1222091009.3153.84.camel@soundwave.ws.pitbpa0.priv.collaborativefusion.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