| From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
|---|---|
| To: | Gregory Williamson <Gregory(dot)Williamson(at)digitalglobe(dot)com> |
| Cc: | Thom Brown <thombrown(at)gmail(dot)com>, Richard Huxton <dev(at)archonet(dot)com>, Harald Armin Massa <haraldarminmassa(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Cannot restart postgresql when increasing max_connections |
| Date: | 2009-01-08 20:06:25 |
| Message-ID: | 1231445185.12947.288.camel@jd-laptop.pragmaticzealot.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, 2009-01-08 at 12:51 -0700, Gregory Williamson wrote:
> Thom Brown wrote:
> <...>
> > I actually mentioned pgPool II to my boss earlier, and it's
> something we
> > will have to seriously consider, but will have to do some research
> first.
>
> We had an application ported from Informix which initially required
> 1000+ connections to handle peak load (one of 4 servers pushed by two
> application servers doing spatial queries).
>
> Using pgPool means we have a max limit of 100 and have almost never
> gone near it -- usually we have 12-25 connections at once and load and
> throughput are higher than they were before.
Not to disparage pgPool, but we have also had great results with
pgBouncer.
Joshua D. Drake
>
--
PostgreSQL
Consulting, Development, Support, Training
503-667-4564 - http://www.commandprompt.com/
The PostgreSQL Company, serving since 1997
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gregory Williamson | 2009-01-08 20:07:14 | Re: Cannot restart postgresql when increasing max_connections |
| Previous Message | Gregory Williamson | 2009-01-08 19:51:44 | Re: Cannot restart postgresql when increasing max_connections |