> > As a rule of thumb, online applications that hold open > > transactions during user interaction are considered to be > > Broken By Design (tm). So I'd slap the programmer/design > > team with - let's use the server box since it doesn't contain > > anything useful. > > Many web applications use persistent database connections for performance > reasons. Persistent connection is not the same as an OPEN transaction BTW. > I suppose it's unlikely for webapps to update a row and then sit and wait a > long time for a hit, so it shouldn't affect most of them. > > However if long running transactions are to be aborted automatically, it > could possibly cause problems with some apps out there. > > Worse if long running transactions are _disconnected_ (not just aborted). -- Sincerely Yours, Denis Perchine ---------------------------------- E-Mail: [EMAIL PROTECTED] HomePage: http://www.perchine.com/dyp/ FidoNet: 2:5000/120.5 ---------------------------------- ---------------------------(end of broadcast)--------------------------- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html
