[Pgpool-general] (pgpool-II) num_init_children misleading?

[Felix J. Ogris]

Hi,

I am not able to open more than num_init_children connections to pgpool-II
(verified with 1.1.1 and 2.0-devel from yesterday's CVS checkout). I thought
that num_init_children is only a hint how many workers should be forked on
startup. I have appended my current config below. Am I right or have I
overseen something?

Best,
Felix

listen_addresses                = '*'
port                            = 5432
socket_dir                      = '/tmp'
pcp_port                        = 9898
pcp_socket_dir                  = '/tmp'
pcp_timeout                     = 10
num_init_children               = 4
child_life_time                 = 300
connection_life_time            = 300
child_max_connection            = 10
logdir                          = '/var/run'
print_timestamp                 = true
connection_cache                = true
health_check_timeout            = 20
health_check_period             = 30
health_check_user               = dbchecker
ignore_leading_white_space      = true
log_statement                   = false
log_hostname                    = false
log_connections                 = false
enable_pool_hba                 = false

replication_mode                = true
replication_strict              = false
replication_timeout             = 60000
load_balance_mode               = true
replication_stop_on_mismatch    = false
insert_lock                     = true

backend_hostname0       = '10.0.0.200'
backend_port0           = 5432
backend_weight0         = 1

backend_hostname1       = '10.0.0.201'
backend_port1           = 5432
backend_weight1         = 1

backend_hostname2       = '10.0.0.202'
backend_port2           = 5432
backend_weight2         = 1