| From: | Guillaume Lelarge <guillaume(at)lelarge(dot)info> |
|---|---|
| To: | Brandon Phelps <bphelps(at)gls(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Connection Pooling |
| Date: | 2011-10-07 20:50:59 |
| Message-ID: | 1318020659.2116.23.camel@localhost.localdomain |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Fri, 2011-10-07 at 15:45 -0400, Brandon Phelps wrote:
> Forgive me, I'm still a bit confused by how max_pool works with num_init_children. First you said that at most I can have 32 clients sending queries, but then you said that each process can handle 4 different connections... so does this mean that I can have 128 connections from pgpool to my postgresql database?
>
That's right. You'll have, from pgpool, a maximum of
num_init_children*max_pool connections (IOW, 128 with your connections).
Out of these 128 connections, only 32 will be active at one time.
I'll try to explain it another way. When client C1 connects to
PostgreSQL via pgpool, it will use one of the four possible connections
of a pooler process.
--
Guillaume
http://blog.guillaume.lelarge.info
http://www.dalibo.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Scott Ribe | 2011-10-07 20:57:56 | Re: Installation woes via Macports on Mac OS X 10.7 |
| Previous Message | René Fournier | 2011-10-07 20:24:11 | Installation woes via Macports on Mac OS X 10.7 |