On Mon, 29 Nov 1999, Oleg Bartunov wrote:
> I'm not concern very much about speed of Postgres but mostly
> about its connection schema. Every new connect to database postgres
> forks another children. It's impossible to work with different
> databases. On my production site I work with persistent connections
> between http (mod_perl) <-> postgres and quite satisfies with efficiency -
> I have 20 httpd running and 20 db backends accordingly.
> This requires some memory, but I could live. Now other developers
> want to use postgres as a db backend in their Web applications and
> also want to have persistence to some another databases.
> If you have N databases and M httpd servers, you will end with
> N*M DB backends. This is too much and I'm afraid my solution
> could be scalable. MySQL seems could works with several databases.
I use (not for production, though) Zope and Postgres (little non
spectacular demo is here: http://sun.med.ru/cgi-bin/Zope.cgi/phd01)
Zope can maintain a database connection or a pool of database
connections. If there is no activity on a connection within a long period
(few hours) Zope closes the connection and reopens it on next access.
Oleg.
----
Oleg Broytmann http://members.xoom.com/phd2/ [EMAIL PROTECTED]
Programmers don't die, they just GOSUB without RETURN.
************
