On Oct 20, 2008, at 10:13 AM, Graham Leggett wrote:
Jim Jagielski wrote:
I thought that was the concern; that the pool wasn't released
immediately. If you disable reuse, then you don't need to
worry about when it is released... or I must be missing something
obvious here :/
Whether the connection is released and returned to the pool (when
pools are used), or when the connection is closed (when pools are
not used), as I understand it now neither of these make any
difference - in both cases, the frontend connection to the client is
flushed - causing a long delay - before the backend is released.
The backend connection is held open during this delay, and isn't
returned to the pool or closed, and this has the double effect of
keeping expensive backend resources tied up for a long time, and
reducing the effectiveness of the connection poool.
Ahhh... I got it now. Basically, as soon as we know we have all the
data from the backend, we should release it.
