"August Zajonc" <junk-pgsql@aontic.com> writes:
> One possible pooling model is to have a bunch of worker connections opened
> to the pgsql instance. Then as sql statements arrive the they are routed
> through an available connection that is open but not doing any work. So 100
> inbound connection may be "multiplexed" to 10 outbound connections to the
> pgsql instance.
[very lucid explanation snipped]
Thanks, makes perfect sense. Really, almost any pooling system can be
looked at that way, since you have N threads that may need
connections, and M connections available. Of course a thread needs to
hang on to a connection throughout any transactions it creates.
-Doug
--
Free Dmitry Sklyarov!
http://www.freesklyarov.org/
We will return to our regularly scheduled signature shortly.