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 062F355DC4 for ; Sun, 20 Mar 2005 17:58:50 +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 39960-01 for ; Sun, 20 Mar 2005 17:58:40 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id F0DA452A64 for ; Sun, 20 Mar 2005 17:58:39 +0000 (GMT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id j2KHwUCH008165; Sun, 20 Mar 2005 12:58:31 -0500 (EST) To: Greg Stark Cc: Josh Berkus , pgsql-performance@postgresql.org Subject: Re: What needs to be done for real Partitioning? In-reply-to: <87br9ehmja.fsf@stark.xeocode.com> References: <200503191202.38089.josh@agliodbs.com> <87br9ehmja.fsf@stark.xeocode.com> Comments: In-reply-to Greg Stark message dated "20 Mar 2005 01:14:01 -0500" Date: Sun, 20 Mar 2005 12:58:30 -0500 Message-ID: <8164.1111341510@sss.pgh.pa.us> From: Tom Lane 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: 200503/388 X-Sequence-Number: 11093 Greg Stark writes: > So I think Phase I should look like: > An ALTER TABLE command to make an inherited table "abstract" in the object > oriented sense. That is, no records can be inserted in the parent table. If > you follow the oracle model this is also where you specify the partition > key. There's no index associated with this partition key though. Check. > A command to create a new partition, essentially syntactic sugar for a > CREATE TABLE with an implied INHERITS clause and a constraint on the > partition key. If you follow the oracle model then you explicitly specify > which range or specific value of the partition key this partition holds. Check. > A command to remove a partition from the partitioned table and turn it into > a regular table. Ugh. Why? You can access the table directly anyway. > A command to take a regular table and turn it into a partition. Double ugh. Verifying that the table matches the partition scheme seems like a lot of ugly, bug-prone, unnecessary code. What's the use case for this anyway? Those last two are *certainly* not Phase I requirements, and I don't think we need them at all ever. regards, tom lane