From: | Jaime Casanova <jcasanov(at)systemguards(dot)com(dot)ec> |
---|---|
To: | Itagaki Takahiro <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Syntax for partitioning |
Date: | 2009-11-17 19:46:01 |
Message-ID: | 3073cc9b0911171146i4709c466re1bd4d662daa16d7@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Nov 12, 2009 at 5:54 AM, Itagaki Takahiro
<itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp> wrote:
> I added psql and pg_dump support to Partitioning Syntax patch.
> Paritioning information can be retrieved with a new system function
> pg_get_partitiondef(parentRelid). Both psql and pg_dump use it.
>
i haven't seen the patch but:
>
> * If a table with the same name already exists when a partition
> is created, the table is re-used as partition. This behavior
> is required for pg_dump to be simple.
>
i guess the table must be empty, if not we should be throw an error...
and i actually prefer some more explicit syntax for this not just
reusing a table
> PARTITION name VALUES LESS THAN { range_upper | MAXVALUE }
> | PARTITION name VALUES IN ( list_value [,...] | DEFAULT )
>
i remember someone making a comment about actually using operators
instead of LESS THEN and family
--
Atentamente,
Jaime Casanova
Soporte y capacitación de PostgreSQL
Asesoría y desarrollo de sistemas
Guayaquil - Ecuador
Cel. +59387171157
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel Stehule | 2009-11-17 19:51:24 | Re: actualised funcs typmod patch |
Previous Message | Marko Tiikkaja | 2009-11-17 19:33:08 | Re: Syntax for partitioning |