Re: Admission Control - Mailing list pgsql-hackers

From Kevin Grittner
Subject Re: Admission Control
Date
Msg-id 4C28C4580200002500032C29@gw.wicourts.gov
Whole thread Raw
In response to Re: Admission Control  (Jesper Krogh <jesper@krogh.cc>)
List pgsql-hackers
Jesper Krogh <jesper@krogh.cc> wrote:
> I have not hit any issues with the work_mem being too high, but
> I'm absolutely sure that I could flood the system if they happened
> to be working at the same time.
OK, now that I understand your workload, I agree that a connection
pool at the transaction level won't do you much good.  Something
which limited the concurrent *query* count, or an execution
admission controller based on resource usage, could save you from
occasional random incidents of resource over-usage.
-Kevin


pgsql-hackers by date:

Previous
From: Magnus Hagander
Date:
Subject: Re: Keepalives win32
Next
From: Bruce Momjian
Date:
Subject: Re: testing plpython3u on 9.0beta2