From: | Stuart Bishop <stuart(at)stuartbishop(dot)net> |
---|---|
To: | Magnus Hagander <mha(at)sollentuna(dot)net> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Postgresql 8.0 and Cancel/Kill backend functions |
Date: | 2005-01-17 02:47:13 |
Message-ID: | 41EB2731.5030806@stuartbishop.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Magnus Hagander wrote:
> The cancel function is implemented. See
> http://developer.postgresql.org/docs/postgres/functions-admin.html#FUNCT
> IONS-ADMIN-SIGNAL-TABLE.
>
> Kill function was considered too dangerous.
Pity - I would have loved this for my test harnesses. I need to drop and
recreate the database between each test and, unless I can kill them, a
test that fails to close a connection victimizes all subsequent tests.
(But not a showstopper in our case - we replace the connect method with
a wrapper and have the harnesses keep track of the connection. This only
leaves connections opened by spawned processes a problem.)
It would be great if this was available as an external method I could
install into a particular database. Hmm... I guess it wouldn't be
difficult to write this - it would simply involve selecting the procpid
from pg_stat_activity and sending a kill signal to it, wouldn't it?
--
Stuart Bishop <stuart(at)stuartbishop(dot)net>
http://www.stuartbishop.net/
From | Date | Subject | |
---|---|---|---|
Next Message | LENGYEL Zoltan | 2005-01-17 04:46:20 | pgpsql help |
Previous Message | Madison Kelly | 2005-01-17 02:41:09 | Re: Iis there anyway to do this(see in message) |