| From: | Greg Smith <greg(at)2ndquadrant(dot)com> |
|---|---|
| To: | Joshua Tolley <eggyknap(at)gmail(dot)com> |
| Cc: | Scott Carey <scott(at)richrelevance(dot)com>, 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-24 05:23:08 |
| Message-ID: | 4C4A78BC.2020101@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Joshua Tolley wrote:
> Relatively minor, but it would be convenient to avoid having to query
> $external_pooler to determine the client_addr of an incoming connection.
>
You suggest this as a minor concern, but I consider it to be one of the
most compelling arguments in favor of in-core pooling. A constant pain
with external poolers is the need to then combine two sources of data in
order to track connections fully, which is something that everyone runs
into eventually and finds annoying. It's one of the few things that
doesn't go away no matter how much fiddling you do with pgBouncer, it's
always getting in the way a bit. And it seems to seriously bother
systems administrators and developers, not just the DBAs.
--
Greg Smith 2ndQuadrant US Baltimore, MD
PostgreSQL Training, Services and Support
greg(at)2ndQuadrant(dot)com www.2ndQuadrant.us
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2010-07-24 05:32:22 | Re: Pooling in Core WAS: Need help in performance tuning. |
| Previous Message | Andres Freund | 2010-07-24 05:13:50 | Re: Pooling in Core WAS: Need help in performance tuning. |