Message-ID: <04f301c38132$7804bc30$6101a8c0@Paulo>
From: "Paulo Scardine" <paulos@cimed.ind.br>
To: "Dave Page" <dpage@vale-housing.co.uk>
Cc: <pgsql-hackers@postgresql.org>
References: <20030921054224.GF3845@filer>
	<20030921142434.S61926-100000@houston.familyhealth.com.au>
	<50096.80.177.99.193.1064140018.squirrel@ssl.vale-housing.co.uk>
Subject: Re: Killing the backend to cancel a long waiting query
Date: Mon, 22 Sep 2003 14:53:45 -0300
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

I can implement it as C functions, I think.
Would be nice to have something like:

Test=# select pg_list_backends();
  pid  | conn_id  |   user   | database  | time |     host      | status
-------+----------+----------+-----------+------+---------------+--------
  4724 | 35445134 | marcelo  | test      | 0:34 | 192.168.2.212 | select
 18737 | 15412337 | postgres | template1 | 0:00 | 192.168.1.65  | idle
 18693 | 11448964 | postgres | test      | 0:00 | 127.0.0.1     | idle
(3 rows)

Test=# select pg_stopquery_pid(4724);
 pg_stopquery_pid
------------------
                0

Is it worth?

--
Paulo Scardine

----- Original Message ----- 
From: "Dave Page" <dpage@vale-housing.co.uk>
> > It would be awesome for phpPGAdmin as well.  eg. Superusers would be
> > able to cancel sql queries that gumby users are running, etc.
>
> I'll second that for pgAdmin. I have times in the past where it would have
> been useful on my own systems as well.
> Regards, Dave.