X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 4F31B3A4F24 for ; Sat, 22 Jan 2005 18:27:20 +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 78548-03 for ; Sat, 22 Jan 2005 18:27:14 +0000 (GMT) Received: from wolff.to (wolff.to [66.93.249.74]) by svr1.postgresql.org (Postfix) with SMTP id AE4333A4F58 for ; Sat, 22 Jan 2005 18:27:13 +0000 (GMT) Received: (qmail 22076 invoked by uid 500); 22 Jan 2005 18:41:24 -0000 Date: Sat, 22 Jan 2005 12:41:24 -0600 From: Bruno Wolff III To: Tatsuo Ishii Cc: marty@outputservices.com, herve@elma.fr, pgsql-performance@postgresql.org Subject: Re: PostgreSQL clustering VS MySQL clustering Message-ID: <20050122184124.GA21889@wolff.to> Mail-Followup-To: Tatsuo Ishii , marty@outputservices.com, herve@elma.fr, pgsql-performance@postgresql.org References: <41F144FE.30902@outputservices.com> <41F14758.4030602@outputservices.com> <20050122.121300.41631131.t-ishii@sra.co.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050122.121300.41631131.t-ishii@sra.co.jp> User-Agent: Mutt/1.5.6i X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.007 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200501/411 X-Sequence-Number: 10101 On Sat, Jan 22, 2005 at 12:13:00 +0900, Tatsuo Ishii wrote: > > Probably VACUUM works well for small to medium size tables, but not > for huge ones. I'm considering about to implement "on the spot > salvaging dead tuples". You are probably vacuuming too often. You want to wait until a significant fraction of a large table is dead tuples before doing a vacuum. If you are scanning a large table and only marking a few tuples as deleted, you aren't getting much bang for your buck.