[pgpool-general: 8073] Re: Advise on reserved_connections

[Tatsuo Ishii]

>> I think it's normal. When a client disconnects to pgpool, the pgpool
>> process becomes "wait for connection request" state. The state of the
>> process is changed only if the kernel chooses the process to wake it
>> up and the pgpool succeeds in accepting the connection request when
>> new connection request arrives from clients. Since only 1 pgpool
>> process accepts new connection request, other pgpool processes remain
>> in "wait for connection request". That's the reason why you see
>> multiple "wait for connection request" state pgpool process.
>> 
>> If you focus on particular pgpool process by using ps command, you
>> should see it changing the process state as time passes.
> 
> However if there are multiple pgpool processes in "wait for connection request", should the postgresql clients get a too many clients response back?
> 
> I'm currently using pgpool 4.1.4 from the postgresql repository for RedHat.

It is possible that even if the ps status is "wait for connection
request", actually the child process is doing something for example
negotiating with client after accepting a connection. The ps status
becomes "idle" after session is established between the client and the
pgpool child process.

Best reagards,
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese:http://www.sraoss.co.jp