We are using PG 7.3.1 and AOLserver 3.3.1 ad13
sometimes users stop their browser or exit
the session in the middle of a long running SQL SELECT.
the Postgres Postmaster process continues to run
and chew CPU time forever.
It seems to me that when a user terminates the http
connection prematurely - the AOLServer should send an
end of transaction signal via the Postgres driver to the
Postmaster backend process and tell it to abort the
This is not happening.
Is there a postgresql.conf parameter that we need to know
about or a secret nsd.tcl parameter that needs to be