| From: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
|---|---|
| To: | "Robert Haas" <robertmhaas(at)gmail(dot)com> |
| Cc: | <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Admission Control Policy |
| Date: | 2009-12-29 00:05:12 |
| Message-ID: | 4B38F358020000250002D9E5@gw.wicourts.gov |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> It seems like it might be helpful, before tackling what you're
talking
> about here, to have some better tools for controlling resource
> utilization. Right now, the tools we have a pretty crude. You
can't
> even nice/ionice a certain backend without risking priority
inversion,
> and there's no sensible way to limit the amount of amount of working
> memory per-query, only per query-node.
>
> http://archives.postgresql.org/pgsql-hackers/2009-10/msg00125.php
I will review and consider. Thanks.
-Kevin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2009-12-29 00:19:49 | Re: ExecTidReScan exprCtxt |
| Previous Message | Robert Haas | 2009-12-29 00:01:13 | Re: Admission Control Policy |