On Thu, Nov 27, 2008 at 9:41 AM, Robert Haas <[EMAIL PROTECTED]> wrote: > On Thu, Nov 27, 2008 at 8:31 AM, Gregory Stark <[EMAIL PROTECTED]> wrote: >>> CREATE PARTITION transaction_2008_11 ON transaction WHERE record_date >>> BETWEEN '2008-11-01' AND '2008-11-30'; >> >> I think the main advantage to a better partitioning method would be teaching >> Postgres about the partition key. Instead of a collection of different >> constraints Postgres would know that "record_date" is *always* the partition >> key. So it wouldn't have to be specified every time you declare a partition. > > Hmm... I thought the main advantage would be that you wouldn't have > to manually add constraints to all of the child tables, and you > wouldn't have to manually add rules/triggers to the parent table to > redirect DML operations. >
ok. what about let CREATE TABLE WITH PARTITIONING to create an entry in a catalog indicating the key of the partition and install the triggers and let the trigger decide if it has the partition to insert the new row (making UPDATE working almost as DELETE+INSERT if it needs to change of partitions) or create the new partition maybe with an apropiate CREATE PARTITION... that way i don't need to create triggers nor inherit tables manually... and because of that maybe we can make possible to add <expr> as partition key... PS: i'm against using CREATE TABLE because we are inventing new syntax but it seems like using ALTER TABLE is a *lot* of work altough ISTM more usefull -- Atentamente, Jaime Casanova Soporte y capacitación de PostgreSQL AsesorÃa y desarrollo de sistemas Guayaquil - Ecuador Cel. +59387171157 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
