X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 90517D1CCD2 for ; Mon, 15 Mar 2004 21:47:04 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 01275-08 for ; Mon, 15 Mar 2004 17:46:58 -0400 (AST) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by svr1.postgresql.org (Postfix) with ESMTP id 751BDD1CCCF for ; Mon, 15 Mar 2004 17:46:55 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.11/8.12.11) with ESMTP id i2FLksJD007888; Mon, 15 Mar 2004 16:46:55 -0500 (EST) To: Mike Bridge Cc: pgsql-performance@postgresql.org Subject: Re: High CPU with 7.4.1 after running for about 2 weeks In-reply-to: References: <7304.1079219828@sss.pgh.pa.us> Comments: In-reply-to Mike Bridge message dated "Sun, 14 Mar 2004 03:10:18 +0000" Date: Mon, 15 Mar 2004 16:46:54 -0500 Message-ID: <7887.1079387214@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200403/206 X-Sequence-Number: 6062 Mike Bridge writes: > But if the client dies, doesn't postgresql normally terminate the > query that that client initiated? Or do I need to set > statement_timeout? The backend generally won't notice that the connection is dead until it next tries to fetch a command from the client. So if the client launches a long-running query and then goes away, the query will normally complete. regards, tom lane