[Pgpool-general] connection pooling

[Mark]

On Fri, Oct 9, 2009 at 12:06 PM, Jaume Sabater <jsabater at gmail.com> wrote:

> On Fri, Oct 9, 2009 at 3:41 PM, Mark <mark at mitsein.net> wrote:
>
> >> Once the maximum configured number of connections is reached, it will
> >> start reusing them. What else would you expect?
> >>
> > Well, I expected exactly that.  I tried an experiment by setting
> > num_init_children to 10 and max_pool to 10.  I fired up one application
> > which initiates 10 db connections.  The next application was not allowed
> a
> > connection.  I expected that pgpool would pool the 10 connections from
> the
> > fist app into one child.  Since it seems that it does not, I don't
> > understand what good max_pool does me.
>
> Connections will be used once they are dropped by previous clients. If
> the maximum limit has been reached and no previous connections from
> clients have been dropped, then the limit has been reached and that is
> the end of the story.
>
> Did you drop your connections (close them) after finishing the queries?
>
>
> Nope.  I didn't run any queries, I just opened connections.  I still don't
understand what max_pool does.  If only one connection can occupy a pgpool
child, I don't see where the pool part comes into play.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://pgfoundry.org/pipermail/pgpool-general/attachments/20091009/38aaea4e/attachment.html>