| From: | Hannu Krosing <hannu(at)krosing(dot)net> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Craig Ringer <craig(at)postnewspapers(dot)com(dot)au>, Matthew Wakeling <matthew(at)flymine(dot)org>, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Pooling in Core WAS: Need help in performance tuning. |
| Date: | 2010-07-22 19:15:44 |
| Message-ID: | 1279826144.14271.5.camel@hvost |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Thu, 2010-07-22 at 14:36 -0400, 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.
not really. in-core != magically-in-right-backend-process
there will still be "an extra hop",only it will be local, between pooler
and backend process.
similar to what currently happens with pgbouncer when you deploy it on
same server and use unix sockets
>
> --
> Robert Haas
> EnterpriseDB: http://www.enterprisedb.com
> The Enterprise Postgres Company
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hannu Krosing | 2010-07-22 19:56:06 | Re: Pooling in Core WAS: Need help in performance tuning. |
| Previous Message | Joshua D. Drake | 2010-07-22 19:15:18 | Re: Pooling in Core WAS: Need help in performance tuning. |