Re: statement_timeout is not cancelling query - Mailing list pgsql-bugs

From Robert Haas
Subject Re: statement_timeout is not cancelling query
Date
Msg-id 603c8f070912150816s5ea81ae4leb96c2ac494748b0@mail.gmail.com
Whole thread Raw
In response to Re: statement_timeout is not cancelling query  (Greg Stark <gsstark@mit.edu>)
Responses Re: statement_timeout is not cancelling query  (Greg Stark <gsstark@mit.edu>)
Re: statement_timeout is not cancelling query  (Alvaro Herrera <alvherre@commandprompt.com>)
List pgsql-bugs
On Tue, Dec 15, 2009 at 11:02 AM, Greg Stark <gsstark@mit.edu> wrote:
> On Tue, Dec 15, 2009 at 3:44 PM, Robert Haas <robertmhaas@gmail.com> wrot=
e:
>> =A0This is an
>> issue that other people have run into in the past, and I don't think
>> we have a good solution. =A0I wonder if we should put some kind of a
>> limit in place so that queries like this will at least fail relatively
>> gracefully with an error message rather than taking down the box.
>
> Eh? That's exactly what's supposed to happen now. When malloc returns
> 0 you're supposed to get a graceful error message and transaction
> abort.

I didn't know that, but it I think by the time malloc returns 0
usually other bad things are happening.  I don't think that's really
an answer.

...Robert

pgsql-bugs by date:

Previous
From: Greg Stark
Date:
Subject: Re: statement_timeout is not cancelling query
Next
From: Robert Haas
Date:
Subject: Re: BUG #5244: Attempting to rollback to a savepoint after receiving an error with state 55000 the process hangs