"Jeff Madison" <[EMAIL PROTECTED]> writes:
> ... What we are seeing is when
> people terminate the application in the middle of a query many times
> postmaster does not see the connection terminate or at least ignores it
> and then proceeds to take a large amount of system resources and never
> dies.
As a general rule, the backend will not notice a connection closure
until it next tries to read from the connection. If you issue some
query that takes a long time to compute, and then give up and abort
your client, the query will still run.
If you're not sure what query you are running, you could attach to
one of the CPU-hogging backends with gdb and issue "p debug_query_string"
to see what it's working on.
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/users-lounge/docs/faq.html
