Ok, I just had a brainstorm for those who want to get a pooling-capable
postmaster up and running.

Do the following:

1.)	Grab the GPL'd AOLserver 3.0 from aolserver.lcs.mit.edu
2.)	Strip out the webserver stuff.
3.)	Write a communications module for AOLserver that implements the
PostgreSQL FE-BE protocol. 
4.)	That module then redirects said communications to a backend
under the pool.
5.)	 Of course, the real postmaster has to run on a different port, as the
AOLserver database driver still will need to initiate connections through
postmaster.
6.)	A few other minor issues will need to be handled, such as
multi-database enabling the AOLserver pool mechanism.

Advantages: AOLserver is multithreaded -- this thing could be made quite fast,
with low latency.

Disadvantages: Adds yet another layer of communication, unless some really
creative coding can be done, thus, post-connect throughput is likely to suffer.
AOLserver is GPL'd, so code lifted from it could not be integrated into the main
PostgreSQL tree.

For those who think they need pooled connections and are not already running
AOLServer...

--
Lamar Owen
WGCR Internet Radio

Wed, 8 Dec 1999 23:37:37 -0500
Lamar Owen <lamar.owen@wgcr.org>
Pooled postgresql backends