From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
---|---|
To: | Josh Berkus <josh(at)agliodbs(dot)com>, Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Declarative partitioning |
Date: | 2015-08-22 03:34:21 |
Message-ID: | 55D7EDBD.50008@BlueTreble.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 8/18/15 12:31 PM, Josh Berkus wrote:
> Also this would be useful for range
> partitions:
>
> CREATE PARTITION ON parent_table USING ( start_value );
>
> ... where start_value is the start range of the new partition. Again,
> easier for users to get correct.
Instead of that, I think it would be more foolproof to do
CREATE PARTITION ON parent_table FOR ( value1, ... );
instead of trusting the user to get the exact start value correct.
Though... I guess there could be value in allowing an exact start value
but throwing an error if it doesn't sit exactly on a boundary. Might
make it less likely to accidentally create the wrong partition.
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Data in Trouble? Get it in Treble! http://BlueTreble.com
From | Date | Subject | |
---|---|---|---|
Next Message | Tomas Vondra | 2015-08-22 04:25:50 | Re: (full) Memory context dump considered harmful |
Previous Message | Michael Paquier | 2015-08-22 00:59:27 | Re: [PATCH] postgres_fdw extension support |