[Pgpool-general] [pgpool-general] num_init_children * max_pool

[Jaume Sabater]

2009/3/16 Willy-Bas Loos <willybas at gmail.com>:

> In the section Configuring pgpool.conf, raw Mode:
> "num_init_children: The number of preforked pgpool-II server processes.
> Default is 32. Please note that cancelling a query creates another
> connection to the backend; thus, a query cannot be cancelled if the
> connections are full."

I understand this statement as:

1. Shall you have the maximum number of connections in use by active
transactions, and
2. Shall you need to cancel one of the existing transactions,
3. As it would need another connection, then
4. You won't be able to cancel the transaction.

That has nothing to do with connection pooling, IMHO.

> Is the "backend" mentioned here the database backend or some pgpool backend?

It means the PostgreSQL server(s).

> If it is the database, then i don't see how this is a connection pooling
> solution. In that case there would still be as many connections to the

As long as you reuse available connections for new client petitions,
if they are available, you are saving connection overhead.

-- 
Jaume Sabater
http://linuxsilo.net/

"Ubi sapientas ibi libertas"