I'm using http 2.0.40 and postgresql 7.3.2 (redhat 9)
When my php script executes a long-running query and user hits the stop button, the query does not terminate and continues to run its full course. Is this the normal behaviour? Further calls from the same browser window using the same connection does not execute and are queued until the first one terminates. This has led to max_connection reached errors.
My question is, is this the normal postgres/php behaviour, and if so, what is the best way to work around this?
pgsql-php by date
|Next:||From: utomo restu||Date: 2003-06-29 01:15:46|
|Subject: blobs didn't work??|
|Previous:||From: David Busby||Date: 2003-06-28 19:09:08|
|Subject: Re: Simulating a POST request|