Re: stopping processes, preventing connections - Mailing list pgsql-general

From Craig Ringer
Subject Re: stopping processes, preventing connections
Date
Msg-id 4BA0BE2E.5080000@postnewspapers.com.au
Whole thread Raw
In response to Re: stopping processes, preventing connections  (Herouth Maoz <herouth@unicell.co.il>)
Responses Re: stopping processes, preventing connections  (Herouth Maoz <herouth@unicell.co.il>)
List pgsql-general
On 17/03/2010 6:32 PM, Herouth Maoz wrote:
>
> On Mar 3, 2010, at 18:01 , Josh Kupershmidt wrote:
>
>> Though next time you see a query which doesn't respond to
>> pg_cancel_backend(), try gathering information about the query and
>> what the backend is doing; either you're doing something unusual (e.g.
>> an app is restarting the query automatically after getting canceled)
>> or perhaps you've stumbled on a bug in Postgres.
>
> Hi. A long time has passed since you made that suggestion, but today we
> stumbled again on a query that wouldn't be canceled. Not only does it
> not respond to pg_cancel_backend(), it also doesn't respond to kill
> -SIGTERM.

Interesting. If you attach gdb to the backend and run "backtrace",
what's the output?

If you strace the backend, what do you see?

--
Craig Ringer

pgsql-general by date:

Previous
From: zhong ming wu
Date:
Subject: Re: return row from plpgsql?
Next
From: Carsten Kropf
Date:
Subject: Bulkdelete and Vacuum operations on custom index