Skip site navigation (1) Skip section navigation (2)

Re: statement_timeout is not cancelling query

From: Greg Stark <gsstark(at)mit(dot)edu>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
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:02:03
Message-ID: 407d949e0912150802x1c303117qbada120dbbd9c3f0@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-bugs
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.

-- 
greg

In response to

Responses

pgsql-bugs by date

Next:From: Robert HaasDate: 2009-12-15 16:16:43
Subject: Re: statement_timeout is not cancelling query
Previous:From: Robert HaasDate: 2009-12-15 15:44:58
Subject: Re: statement_timeout is not cancelling query

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group