| 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-23 15:58:27 |
| Message-ID: | 1279900707.26952.4.camel@hvost |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Thu, 2010-07-22 at 20:57 -0400, Robert Haas wrote:
> On Thu, Jul 22, 2010 at 3:15 PM, Hannu Krosing <hannu(at)krosing(dot)net> wrote:
> > 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
>
> Well, how about if we arrange it so it IS in the right backend
> process? I don't believe magic is required.
Do you have any design in mind, how you can make it so ?
---------------
Hannu
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joshua D. Drake | 2010-07-23 16:52:37 | Re: Pooling in Core WAS: Need help in performance tuning. |
| Previous Message | Joshua Tolley | 2010-07-23 15:55:35 | Re: Pooling in Core WAS: Need help in performance tuning. |