query not aborted upon connection aborted?

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