Re: Killing the backend to cancel a long waiting query
От | Paulo Scardine |
---|---|
Тема | Re: Killing the backend to cancel a long waiting query |
Дата | |
Msg-id | 04f301c38132$7804bc30$6101a8c0@Paulo обсуждение исходный текст |
Ответ на | Re: Killing the backend to cancel a long waiting query (Kevin Brown <kevin@sysexperts.com>) |
Ответы |
Re: Killing the backend to cancel a long waiting query
|
Список | pgsql-hackers |
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 | select18737 | 15412337 | postgres | template1 | 0:00 | 192.168.1.65 | idle18693 | 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.
В списке pgsql-hackers по дате отправления: