From: | Bill Moran <wmoran(at)potentialtech(dot)com> |
---|---|
To: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
Cc: | Alan McKay <alan(dot)mckay(at)gmail(dot)com>, Postgres General Postgres General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: limiting query time and/or RAM |
Date: | 2009-09-17 19:31:12 |
Message-ID: | 20090917153112.3ebb2649.wmoran@potentialtech.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
In response to Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>:
> On Thu, Sep 17, 2009 at 12:56 PM, Alan McKay <alan(dot)mckay(at)gmail(dot)com> wrote:
> > Is there any way to limit a query to a certain amount of RAM and / or
> > certain runtime?
> >
> > i.e. automatically kill it if it exceeds either boundary?
> >
> > We've finally narrowed down our system crashes and have a smoking gun,
> > but no way to fix it in the immediate term. This sort of limit would
> > really help us.
>
> Generally speaking work_mem limits ram used. What are your
> non-default postgresql.conf settings?
work_mem limits memory usage _per_sort_.
A big query can easily have many sorts. Each sort will be limited to
work_mem memory usage, but the total could be much higher.
The only way I can think is to set a per-process limit in the OS and allow
the OS to kill a process when it gets out of hand. Not ideal, though.
--
Bill Moran
http://www.potentialtech.com
http://people.collaborativefusion.com/~wmoran/
From | Date | Subject | |
---|---|---|---|
Next Message | Scott Marlowe | 2009-09-17 19:35:04 | Re: limiting query time and/or RAM |
Previous Message | Martin Gainty | 2009-09-17 19:29:24 | Re: 'Weird' errors |