| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Greg Stark <gsstark(at)mit(dot)edu> |
| Cc: | Craig Ringer <craig(at)postnewspapers(dot)com(dot)au>, Mark Williamson <thetazzbot(at)gmail(dot)com>, pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: statement_timeout is not cancelling query |
| Date: | 2009-12-15 16:16:43 |
| Message-ID: | 603c8f070912150816s5ea81ae4leb96c2ac494748b0@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Tue, Dec 15, 2009 at 11:02 AM, Greg Stark <gsstark(at)mit(dot)edu> wrote:
> On Tue, Dec 15, 2009 at 3:44 PM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>> This is an
>> issue that other people have run into in the past, and I don't think
>> we have a good solution. I 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2009-12-15 16:58:49 | Re: BUG #5244: Attempting to rollback to a savepoint after receiving an error with state 55000 the process hangs |
| Previous Message | Greg Stark | 2009-12-15 16:02:03 | Re: statement_timeout is not cancelling query |