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 691DF3A3C24 for ; Thu, 11 Nov 2004 22:49:05 +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 76642-09 for ; Thu, 11 Nov 2004 22:48:54 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id 71F973A4669 for ; Thu, 11 Nov 2004 22:48:56 +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 iABMmqIM012505; Thu, 11 Nov 2004 17:48:52 -0500 (EST) To: "Paul B. Anderson" Cc: pgsql-admin@postgresql.org Subject: Re: Large transaction problem In-reply-to: <4193E45A.7050000@pnlassociates.com> References: <4193C282.2040904@pnlassociates.com> <11555.1100207255@sss.pgh.pa.us> <4193E45A.7050000@pnlassociates.com> Comments: In-reply-to "Paul B. Anderson" message dated "Thu, 11 Nov 2004 17:14:50 -0500" Date: Thu, 11 Nov 2004 17:48:52 -0500 Message-ID: <12504.1100213332@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/101 X-Sequence-Number: 15486 "Paul B. Anderson" writes: > After I restart postgresql, I execute vacuum several times in sql until > it succeeds. Then, everything else works OK again. > After I clear the problem, > select count(*) from archive > takes a second but, before the problem is cleared, it takes about 30 > seconds and then gives the canceled by user response. This all sounds exactly like an overly enthusiastic statement_timeout. What you are doing to "clear the problem" is merely to populate the disk cache sufficiently that your query finishes before timing out. regards, tom lane