| From: | Joshua Tolley <eggyknap(at)gmail(dot)com> |
|---|---|
| To: | Scott Carey <scott(at)richrelevance(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Craig Ringer <craig(at)postnewspapers(dot)com(dot)au>, Matthew Wakeling <matthew(at)flymine(dot)org>, "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: Pooling in Core WAS: Need help in performance tuning. |
| Date: | 2010-07-23 15:55:35 |
| Message-ID: | 4c49bb81.17bb720a.42c2.1de8@mx.google.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Thu, Jul 22, 2010 at 02:44:04PM -0700, Scott Carey wrote:
> On Jul 22, 2010, at 11:36 AM, Robert Haas wrote:
> > On Mon, Jul 12, 2010 at 6:58 AM, Craig Ringer
> > <craig(at)postnewspapers(dot)com(dot)au> wrote:
> >> So rather than asking "should core have a connection pool" perhaps
> >> what's needed is to ask "what can an in-core pool do that an external
> >> pool cannot do?"
> >
> > Avoid sending every connection through an extra hop.
> >
>
> Dynamically adjust settings based on resource usage of the DB.
>
Relatively minor, but it would be convenient to avoid having to query
$external_pooler to determine the client_addr of an incoming connection.
--
Joshua Tolley / eggyknap
End Point Corporation
http://www.endpoint.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hannu Krosing | 2010-07-23 15:58:27 | Re: Pooling in Core WAS: Need help in performance tuning. |
| Previous Message | Torsten Zühlsdorff | 2010-07-23 09:22:18 | Re: Using more tha one index per table |