[Pgpool-general] pgpool.conf max_pool question

[Tatsuo Ishii]

> Hi,
> 
> i am a first time user of pgpool on debian stable Version: 2.5.2-1
> 
> i configured pgpool like this:
> 
> # number of pre-forked child process
> num_init_children = 32
> 
> # numer of connection pool allowed for a child process.
> max_pool = 2
> 
> now i have 64 database connections but all with the same username/database 
> pair, but manual says:
> 
> "pgpool will make a new connection if there's no user name and database name 
> pair yet."
> 
>  ps ax | grep 'postgres: myuser mydatabase' | grep -v grep | wc -l
>  ps ax | grep '/usr/sbin/pgpool' | grep -v grep | wc -l
> 
>  64

This should be 32. I cannot reproduce your problem here. Are your sure
that username/database pairs are same? And you should use same
protocol version. BTW 2.5.2 is the fairly old version. The latest one
is 3.0.2. Can you try out?
--
Tatsuo Ishii
SRA OSS, Inc. Japan

>  33
> 
> I had set max_pool = 2 because there is sometimes a different user connecting 
> but most of the time it is the same user to the same database. Is pgpool 
> working correct? Or did i miss something?
> 
> Another thing which is should be mentioned in the docs is the fact, that 
> pgpool has a listen queue and connections exceeding num_init_children are 
> queued. postgresql throws an error immedeatly. It would be nice if pgpool 
> does so too (or can be configured) as there is no need to have a backlog in 
> web environment. It is often better to not connect than to wait for an open 
> slot. 
> 
> kind regards,
> janning
> _______________________________________________
> Pgpool-general mailing list
> Pgpool-general at pgfoundry.org
> http://pgfoundry.org/mailman/listinfo/pgpool-general
>