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 B028DD1B517 for ; Thu, 23 Oct 2003 13:18:14 +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 47320-07 for ; Thu, 23 Oct 2003 10:17:47 -0300 (ADT) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by svr1.postgresql.org (Postfix) with ESMTP id 4373FD1B510 for ; Thu, 23 Oct 2003 10:17:43 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.10/8.12.10) with ESMTP id h9NDHfit029065; Thu, 23 Oct 2003 09:17:41 -0400 (EDT) To: Andrew Sullivan Cc: pgsql-performance@postgresql.org Subject: Re: vacuum locking In-reply-to: <20031023101425.GC16878@libertyrms.info> 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> <20031023101425.GC16878@libertyrms.info> Comments: In-reply-to Andrew Sullivan message dated "Thu, 23 Oct 2003 06:14:25 -0400" Date: Thu, 23 Oct 2003 09:17:41 -0400 Message-ID: <29064.1066915061@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200310/598 X-Sequence-Number: 4346 Andrew Sullivan writes: > 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? Maybe, but only if it actually had reason to use a ton of memory --- that is, it were recycling a very large number of tuples in a single table. IIRC that didn't seem to be the case here. regards, tom lane