[pgpool-general: 8147] Re: allocation of child processes is constantly growing

Nikola(HM) nikm71 at hotmail.com
Wed May 11 16:46:39 JST 2022

Thanks for the reply. But still. The situation is this.

The microservice connects to the child process and through it to the 
database. And this connection remains. Then the same microservice with 
the same user to the same database creates a new connection with another 
child process rather than reusing the old one that already exists. Why?


On 11.05.2022 09:29, Tatsuo Ishii wrote:
> Hi,
>> Hello,
>> We are running an application in Kubernetes. Pgpool also works in
>> Kubernetes. Each microservice has its own PostgreSQL
>> database. Microservices are written in Java and connect to their
>> databases via Pgpool .
>> We have a very hot issue with Pgpool.
>> Even in quiet mode, when there is no activity, the number of busy
>> child processes and, accordingly, connections to databases is
>> constantly growing on PostgreSQL and on  and does not decrease,
>> reaching the limit. It turns out that microservices make new
>> connections to the database each time through a new child process, and
>> do not reuse the existing one.
>> Could you please tell me why this is happening.
>> Explain, please, the mechanism of allocation of child process in
>> Pgpool for client connections.
>> When an existing client connection to a child process is reused and
>> when not?
> Please see the FAQ:
> https://pgpool.net/mediawiki/index.php/FAQ#Is_connection_pool_cache_shared_among_pgpool_process.3F
> Best reagards,
> --
> Tatsuo Ishii
> SRA OSS, Inc. Japan
> English: http://www.sraoss.co.jp/index_en.php
> Japanese:http://www.sraoss.co.jp

More information about the pgpool-general mailing list