| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Greg Stark <gsstark(at)mit(dot)edu>, 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 18:27:07 |
| Message-ID: | 603c8f070912151027i56f074few50a9adcd524942b@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Tue, Dec 15, 2009 at 1:23 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
>> If we're to do anything about this, it is spilling the trigger queue so
>> it doesn't eat an unbounded amount of memory.
>
> Of course, the reason nothing much has been done about that is that
> by the time your trigger queue is long enough to cause such an issue,
> you're screwed anyway --- actually executing all those triggers would
> take longer than you'll want to wait.
What is the best way to go about doing that, anyway?
...Robert
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2009-12-15 18:29:25 | Re: BUG #5242: ODBC driver v8.4.1 crashed |
| Previous Message | Tom Lane | 2009-12-15 18:23:40 | Re: statement_timeout is not cancelling query |