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 07794566C4 for ; Mon, 21 Mar 2005 22:11:13 +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 92384-05 for ; Mon, 21 Mar 2005 22:11:07 +0000 (GMT) Received: from flake.decibel.org (flake.decibel.org [67.100.216.10]) by svr1.postgresql.org (Postfix) with ESMTP id 5FA19566A0 for ; Mon, 21 Mar 2005 22:11:07 +0000 (GMT) Received: by flake.decibel.org (Postfix, from userid 1001) id 37C3815258; Mon, 21 Mar 2005 16:11:09 -0600 (CST) Date: Mon, 21 Mar 2005 16:11:09 -0600 From: "Jim C. Nasby" To: Tom Lane Cc: Alvaro Herrera , PFC , Josh Berkus , pgsql-performance@postgresql.org Subject: Re: What needs to be done for real Partitioning? Message-ID: <20050321221109.GT51784@decibel.org> References: <200503191202.38089.josh@agliodbs.com> <20050319225624.GA8467@dcc.uchile.cl> <3404.1111277153@sss.pgh.pa.us> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3404.1111277153@sss.pgh.pa.us> X-Operating-System: FreeBSD 4.11-RELEASE i386 X-Distributed: Join the Effort! http://www.distributed.net User-Agent: Mutt/1.5.6i X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.024 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200503/424 X-Sequence-Number: 11129 On Sat, Mar 19, 2005 at 07:05:53PM -0500, Tom Lane wrote: > Alvaro Herrera writes: > > We probably also need multi-table indexes. > > As Josh says, that seems antithetical to the main point of partitioning, > which is to be able to rapidly remove (and add) partitions of a table. > If you have to do index cleaning before you can drop a partition, what's > the point of partitioning? Why would you need to do index cleaning first? Presumably the code that goes to check a heap tuple that an index pointed at to ensure that it was visible in the current transaction would be able to recognize if the partition that tuple was in had been removed, and just ignore that index entry. Granted, you'd need to clean the index up at some point (presumably via vacuum), but it doesn't need to occur at partition drop time. -- Jim C. Nasby, Database Consultant decibel@decibel.org Give your computer some brain candy! www.distributed.net Team #1828 Windows: "Where do you want to go today?" Linux: "Where do you want to go tomorrow?" FreeBSD: "Are you guys coming, or what?"