-Original Message-
From: pgpool-general-boun...@pgfoundry.org [mailto:pgpool-general-
boun...@pgfoundry.org] On Behalf Of Guillaume Lelarge
Sent: Friday, August 19, 2011 9:30 AM
To: Johnny Tan
Cc: pgpool-general@pgfoundry.org
Subject: Re: [Pgpool-general] connections not pooling
I guess the disconnected client won't be happy about that :) pgPool is
really usefull when you have lots of small sessions. If you only have
some long connections, then pgpool pooling mode won't be of any use.
Perhaps the other modes, but not the pooling one. And in this case, you
should
Thanks Tatsuo.
I originally started with that (num_init_children=16), but then when
all connections were used, even though they were idle, new connections
would hang forever. When I set client_idle_limit greater than 0, we
got errors like this:
PGError: ERROR: connection terminated due to client
I originally started with that (num_init_children=16), but then when
all connections were used, even though they were idle, new connections
would hang forever.
Sure, it's normal behaviour for pgPool. The pooling is done in session
mode. It means that once a session is started, the pgpool
I setup pgpool-3.0.4 (config attached) in our staging environment. In
staging, we have 5 servers which make a total of 35 connections
(multiple rails thin webservers on each).
In pgpool, I see 35 connections from the 5 servers. In the backend db,
I expected to see less than 35, but I don't. I see
