Shridhar Daithankar <[EMAIL PROTECTED]> writes:That situation is usually handled by means of a TP Monitor that keeps open database connections ( e.g, CICS + DB2 ).
But database is not webserver. It is not suppose to handle tons of concurrent requests. That is a fundamental difference.
And in one fell swoop you've dismissed the entire OLTP database industry.
Have you ever called a travel agent and had him or her look up a fare in the
airline database within seconds? Ever placed an order over the telephone? Ever used a busy database-backed web site?
I think there is some confusion between "many concurrent connections + short transactions" and "many connect / disconnect + short transactions" in some of this discussion.
OLTP systems typically fall into the first case - perhaps because their db products do not have fast connect / disconnect :-). Postgresql plus some suitable middleware (e.g Php) will handle this configuration *with* its current transaction model.
I think you are actually talking about the connect / disconnect speed rather than the *transaction* model per se.
best wishes
Mark
---------------------------(end of broadcast)--------------------------- TIP 4: Don't 'kill -9' the postmaster
