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 8EDFDD1B52D for ; Thu, 23 Oct 2003 10:14:55 +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 17871-06 for ; Thu, 23 Oct 2003 07:14:26 -0300 (ADT) Received: from mail.libertyrms.com (unknown [209.167.124.227]) by svr1.postgresql.org (Postfix) with ESMTP id 39A36D1B529 for ; Thu, 23 Oct 2003 07:14:23 -0300 (ADT) Received: from [10.1.2.130] (helo=dba2) by mail.libertyrms.com with esmtp (Exim 3.22 #3 (Debian)) id 1ACcU5-0007gY-00 for ; Thu, 23 Oct 2003 06:14:25 -0400 Received: by dba2 (Postfix, from userid 1019) id B5300CD6A; Thu, 23 Oct 2003 06:14:25 -0400 (EDT) Date: Thu, 23 Oct 2003 06:14:25 -0400 From: Andrew Sullivan To: pgsql-performance@postgresql.org Subject: Re: vacuum locking Message-ID: <20031023101425.GC16878@libertyrms.info> Mail-Followup-To: Andrew Sullivan , pgsql-performance@postgresql.org References: <16272.318.870000.93584@gargle.gargle.HOWL> <3F9006BF.40906@persistent.co.in> <16272.4154.489000.227676@gargle.gargle.HOWL> <200310170936.25997.josh@agliodbs.com> <16272.32044.80671.948532@jump.bivio.com> <16279.4988.496000.539525@gargle.gargle.HOWL> <25480.1066872467@sss.pgh.pa.us> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <25480.1066872467@sss.pgh.pa.us> User-Agent: Mutt/1.5.4i X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200310/597 X-Sequence-Number: 4345 On Wed, Oct 22, 2003 at 09:27:47PM -0400, Tom Lane wrote: > trace. What is causing that? Not VACUUM I don't think. It doesn't have > any huge memory demand. But swapping out processes could account for What about if you've set vacuum_mem too high? A -- ---- Andrew Sullivan 204-4141 Yonge Street Afilias Canada Toronto, Ontario Canada M2P 2A8 +1 416 646 3304 x110