[Pgpool-general] connections not pooling

[Guillaume Lelarge]

On Fri, 2011-08-19 at 17:12 -0400, Johnny Tan wrote:
> >> 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 process for
> > this session is blocked. It cannot handle any other request.
> 
> So, the only option is to more or less force a client disconnect, so
> another client can come in and reuse the same connection? In that
> case, I could set max_connections=1. Which seems odd to me, but in
> theory, should let us take advantage of pooling, right?
> 

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 better look at pgBouncer and its transaction or query pooling
mode.


-- 
Guillaume
  http://blog.guillaume.lelarge.info
  http://www.dalibo.com