On Fri, Jan 24, 2003 at 11:24:52PM +0000, Steve Manning wrote: > Could someone who knows about these things say what happens to a > Postgres DB connection if a request closes prematurely i.e if the user > hits stop or closes the browser before a query has finished is the DB > conn returned to the pool before the query returns and can this have any > nasty effects?
As far as I've ever known, nothing special happens, the query runs to completion as normal. That's certainly what I've always seen happen with Oracle. I am not familiar with the nsdb internal, but AFAIK the ns_db driver and thus Postgres (or Oracle) doesn't even have any way of KNOWING whether or not the web browser is still connected to the web server or not. But... I suspect Steve M. is wondering about the second of these threads: http://openacs.org/forums/message-view?message_id=74443 http://openacs.org/forums/message-view?message_id=74451 where Dan Lieberman said: > Having said that - there is a curious problem with PG. When the user > disconnects by STOP or closing the browser - the PG process running > the SELECT NEVER finishes. Thats why i called it a zombie (even > tho' thats an incorrect definion by unix terms) - I would have > thought that the process WOULD complete the SELECT and drop its > results into the bit bucket. > > This is whats really troubling me. It smells like a bug in the > AOLServer PG driver Now that I think of it, I'm wondering about that to. Is the behavior Dan's describing in fact possible? Is there any possible interaction between the conn and the db driver in AOLserver? -- Andrew Piskorski <[EMAIL PROTECTED]> http://www.piskorski.com
