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 29842D1B21B for ; Thu, 8 Jul 2004 15:25:56 -0300 (ADT) 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 15880-05 for ; Thu, 8 Jul 2004 18:25:54 +0000 (GMT) Received: from tht.net (vista.tht.net [216.126.88.2]) by svr1.postgresql.org (Postfix) with ESMTP id DF8E9D1B20E for ; Thu, 8 Jul 2004 15:25:52 -0300 (ADT) Received: from [134.22.68.4] (dyn-68-4.tor.dsl.tht.net [134.22.68.4]) by tht.net (Postfix) with ESMTP id 1DFEE76B65; Thu, 8 Jul 2004 14:25:33 -0400 (EDT) Subject: Re: vacuum_mem From: Rod Taylor To: Litao Wu Cc: "pgsql-performance@postgresql.org" In-Reply-To: <20040708180343.88032.qmail@web13121.mail.yahoo.com> References: <20040708180343.88032.qmail@web13121.mail.yahoo.com> Content-Type: text/plain Message-Id: <1089311129.5999.219.camel@jester> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Thu, 08 Jul 2004 14:25:30 -0400 Content-Transfer-Encoding: 7bit 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: 200407/39 X-Sequence-Number: 7430 > It seems vacuum_mem does not have performance > effect at all. Wrong conclusion. It implies that your test case takes less than 64M of memory to track your removed tuples. I think it takes 8 bytes to track a tuple for vacuuming an index, which means it should be able to track 800000 deletions. Since you're demonstration had 750000 for removal, it's under the limit. Try your test again with 32MB; it should make a single sequential pass on the table, and 2 passes on each index for that table. Either that, or do a few more aborted updates.