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 9CA56D1B4E6 for ; Fri, 17 Oct 2003 23:12:34 +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 49713-01 for ; Fri, 17 Oct 2003 20:12:06 -0300 (ADT) Received: from jump.bivio.com (jump.bivio.com [216.87.82.232]) by svr1.postgresql.org (Postfix) with ESMTP id F2C33D1B4E5 for ; Fri, 17 Oct 2003 20:11:58 -0300 (ADT) Received: (from nagler@localhost) by jump.bivio.com (8.11.6/8.11.6) id h9HNBxJ06778; Fri, 17 Oct 2003 17:11:59 -0600 X-Authentication-Warning: jump.bivio.com: nagler set sender to nagler@bivio.biz using -f From: Rob Nagler MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16272.30527.120343.547492@jump.bivio.com> Date: Fri, 17 Oct 2003 17:11:59 -0600 To: pgsql-performance@postgresql.org Subject: Re: vacuum locking In-Reply-To: References: <16272.318.870000.93584@gargle.gargle.HOWL> <3F9006BF.40906@persistent.co.in> <16272.4154.489000.227676@gargle.gargle.HOWL> X-Mailer: VM 6.96 under Emacs 20.7.1 Organization: bivio Software Artisans, Inc. X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200310/487 X-Sequence-Number: 4235 Manfred Koizar writes: > ISTM you are VACCUMing too aggressively. You are reclaiming less than > 1% and 0.005%, respectively, of tuples. I would increase FSM settings > to ca. 1000 fsm_relations, 100000 fsm_pages and VACUUM *less* often, > say every two hours or so. I did this. We'll see how it goes. > ... or configure autovacuum to VACUUM a table when it has 10% dead > tuples. This solution doesn't really fix the fact that VACUUM consumes the disk while it is running. I want to avoid the erratic performance on my web server when VACUUM is running. mfg, Rob