| From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
|---|---|
| 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:18 |
| Message-ID: | 1279826118.22360.137.camel@jd-desktop.unknown.charter.com |
| 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.
Let's extend this shall we:
Avoid adding yet another network hop
Remove of a point of failure
Reduction of administrative overhead
Integration into our core authentication mechanisms
Greater flexibility in connection control
And, having connection pooling in core does not eliminate the use of an
external pool where it makes since.
JD
--
PostgreSQL.org Major Contributor
Command Prompt, Inc: http://www.commandprompt.com/ - 509.416.6579
Consulting, Training, Support, Custom Development, Engineering
http://twitter.com/cmdpromptinc | http://identi.ca/commandprompt
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hannu Krosing | 2010-07-22 19:15:44 | Re: Pooling in Core WAS: Need help in performance tuning. |
| Previous Message | Robert Haas | 2010-07-22 18:36:27 | Re: Pooling in Core WAS: Need help in performance tuning. |