X-Original-To: pgsql-php-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.193]) by svr1.postgresql.org (Postfix) with ESMTP id 40095310358 for ; Sat, 28 Jun 2003 21:09:26 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (svr1.postgresql.org [64.117.224.193]) (amavisd-new, port 10024) with ESMTP id 23660-06 for ; Sat, 28 Jun 2003 18:09:15 -0300 (ADT) Received: from mars.www.jobsfactory.com (unknown [202.126.178.202]) by svr1.postgresql.org (Postfix) with ESMTP id 0C4223104D6 for ; Sat, 28 Jun 2003 18:09:13 -0300 (ADT) Received: from p424 (bb220-255-123-217.singnet.com.sg [220.255.123.217]) by mars.www.jobsfactory.com (Rockliffe SMTPRA 4.5.6) with ESMTP id for ; Sun, 29 Jun 2003 05:11:50 +0800 Message-ID: <001b01c33db9$8bdcbfd0$0200a8c0@p424> From: "Eric Koh" To: Subject: query not aborted upon connection aborted? Date: Sun, 29 Jun 2003 05:09:21 +0800 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0018_01C33DFC.99CDCC40" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1158 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-Archive-Number: 200306/34 X-Sequence-Number: 2098 This is a multi-part message in MIME format. ------=_NextPart_000_0018_01C33DFC.99CDCC40 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi, 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 but= ton, 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 te= rminates. 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? Thanks! ------=_NextPart_000_0018_01C33DFC.99CDCC40 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hi,
 
I'm using http=20 2.0.40 and postgresql 7.3.2 (redhat=20 9)
 
When my php script executes a long-running= query=20 and user hits the stop button, the query= does not=20 terminate and continues to run its full = course.=20 Is this the normal behaviour? Further calls from the same browser window us= ing=20 the same connection does not execute and are queued until the first one=20 terminates. This has led to max_connection reached errors.
 
My question is, is this the normal postgre= s/php=20 behaviour, and if so, what is the best way to work around this?
 
Thanks!
------=_NextPart_000_0018_01C33DFC.99CDCC40--