>> 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? johnny _______________________________________________ Pgpool-general mailing list Pgpool-general@pgfoundry.org http://pgfoundry.org/mailman/listinfo/pgpool-general
