Re: Connection Pooling directly on Postgres Server

On 07.09.2007 10:16, Denis Gasparin wrote:
> What to do you think about this?

I think there is no need for this and it's the wrong place to implement it.

Why should PostgreSQL do something to work around broken application 
design? An application that closes its database connection just to 
create a new one a second later is broken.

In this particular case the thing to fix is Apache's legacy 
architecture. Prefork based web servers are really something from the 
last decade.

Consider Lighttpd, Litespeed or Zeus and connect a fixed amount of 
PHP/Perl/Python/Ruby/Lua workers via FCGI. Each worker keeps a 
persistent connection to PG and load is distributed over the workers.


-- 
Regards,
Hannes Dorbath