From: Tom Lane <tgl@sss.pgh.pa.us>
To: Greg Stark <gsstark@mit.edu>
Cc: Josh Berkus <josh@agliodbs.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: What needs to be done for real Partitioning?
Date: Sun, 20 Mar 2005 12:58:30 -0500
Message-ID: <8164.1111341510@sss.pgh.pa.us> (raw)
In-Reply-To: <87br9ehmja.fsf@stark.xeocode.com>
References: <200503191202.38089.josh@agliodbs.com>
<87br9ehmja.fsf@stark.xeocode.com>
Greg Stark <gsstark@mit.edu> 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: tgl@sss.pgh.pa.us, gsstark@mit.edu, josh@agliodbs.com
Subject: Re: What needs to be done for real Partitioning?
In-Reply-To: <8164.1111341510@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox