Message-ID: <007701c37e0f$4fc1b550$6101a8c0@Paulo>
From: "Paulo Scardine" <paulos@cimed.ind.br>
To: <pgsql-hackers@postgresql.org>
Cc: <pgsql-odbc@postgresql.org>, <pgsql-interfaces@postgresql.org>
References: <Pine.LNX.4.33.0309161858470.30978-100000@leary.csoft.net>
	<2054.1063808792@sss.pgh.pa.us> <3F69A6DE.1050002@bigfoot.com>
Subject: Killing the backend to cancel a long waiting query
Date: Thu, 18 Sep 2003 15:04:32 -0300
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

There are many interfaces that doesn't support canceling a long query other
than killing the application or killing the backend using the server
operational system.

I've searched the docs, faqs and list archives; seen a lot of questions but
no answers.

So I hacked a small pggetpid and pgkillpid C functions, and now I can learn
the backend's PID, start the query in a new thread, and kill the backend
using another connection if I want. Its ugly, I know, but worked wonderfully
with ODBC, the Delphi developers here and the users are very happy.

Questions are:
1) is there a better way to do that?
2) is it safe to kill the backend this way (other than an user killing the
wrong postgres owned proccess)?
3) is this useful for anyone else?

Regards,
--
Paulo Scardine