If you're not dying to use Apache, I might recommend taking a look at
AOLServer (http://www.aolserver.com)... it's thread-safe,
multi-threaded, db-connection pooling, lightweight web server...
extrememly fast (powers most of the major server at AOL serving 100+
conns/sec), easy to connect to postgresql (http://www.openacs.org), and
TCL API... if you need each virtual host to have its own db pools, you
can use AOLServer's nsvhr and nsunix modules to set up virtual hosts on
unix sockets... if the virtual hosts can share db pools, then you can
use the VAT module (http://zmbh.com/discussion/vat/)... Since it's got
it all built it, you might look into it...
-jag
Ryan Mahoney wrote:
> Has anyone on this list used sql-relay with pgsql? If you're not familiar
> with it, you can find out more at:
> http://www.firstworks.com/sqlrelay.html. My primary interest is to reap
> the benefits of connection pooling on an Apache/PHP/PostgreSQL
> configuration. We're setting up a farm of webservers to talk to our
DB, if
> we use PHP pooling, we may end up with thousands un-needed open
> connections. Sql-relay looks a bit involved to set up - but just may be
> worth it.