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 451CA558AC for ; Sun, 20 Mar 2005 04:43:04 +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 61986-01 for ; Sun, 20 Mar 2005 04:43:03 +0000 (GMT) Received: from tht.net (vista.tht.net [216.126.88.2]) by svr1.postgresql.org (Postfix) with ESMTP id C6EFD556D3 for ; Sun, 20 Mar 2005 04:43:01 +0000 (GMT) Received: from dyn-70-66.tor.dsl.tht.net (dyn-70-66.tor.dsl.tht.net [134.22.70.66]) by tht.net (Postfix) with ESMTP id CB2207787F; Sat, 19 Mar 2005 23:43:04 -0500 (EST) Subject: Re: What needs to be done for real Partitioning? From: Rod Taylor To: Alvaro Herrera Cc: pgsql-performance@postgresql.org, Josh Berkus , PFC , Tom Lane In-Reply-To: <20050320042917.GA25831@dcc.uchile.cl> References: <200503191202.38089.josh@agliodbs.com> <20050319225624.GA8467@dcc.uchile.cl> <3404.1111277153@sss.pgh.pa.us> <20050320042917.GA25831@dcc.uchile.cl> Content-Type: text/plain Date: Sat, 19 Mar 2005 23:42:17 -0500 Message-Id: <1111293737.1132.358.camel@home> Mime-Version: 1.0 X-Mailer: Evolution 2.2.0 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.011 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200503/384 X-Sequence-Number: 11089 On Sun, 2005-03-20 at 00:29 -0400, Alvaro Herrera wrote: > 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? > > Hmm. You are right, but without that we won't be able to enforce > uniqueness on the partitioned table (we could only enforce it on each > partition, which would mean we can't partition on anything else than > primary keys if the tables have one). IMHO this is something to > consider. Could uniqueness across partitions be checked for using a mechanism similar to what a deferred unique constraint would use (trigger / index combination)?