X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 75BA43A44DB for ; Thu, 11 Nov 2004 21:07:52 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 40931-08 for ; Thu, 11 Nov 2004 21:07:39 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id E79B63A4404 for ; Thu, 11 Nov 2004 21:07:39 +0000 (GMT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id iABL7ZRF011556; Thu, 11 Nov 2004 16:07:35 -0500 (EST) To: "Paul B. Anderson" Cc: pgsql-admin@postgresql.org Subject: Re: Large transaction problem In-reply-to: <4193C282.2040904@pnlassociates.com> References: <4193C282.2040904@pnlassociates.com> Comments: In-reply-to "Paul B. Anderson" message dated "Thu, 11 Nov 2004 14:50:26 -0500" Date: Thu, 11 Nov 2004 16:07:35 -0500 Message-ID: <11555.1100207255@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200411/99 X-Sequence-Number: 15484 "Paul B. Anderson" writes: > My postgresql.conf file had a 10 second timeout and the large database > required more than 10 seconds for the vacuum. It seems that this left > postmaster and/or the particular database in a state where any SQL > against that database gave the same error response about being canceled > by the user. Hmm, I couldn't duplicate this. I thought maybe the vacuum wasn't releasing some lock after it failed, but there's no sign of such a problem. Are you sure it isn't just that all your queries were running into the timeout? regards, tom lane