On 08/21/2015 08:34 PM, Jim Nasby wrote: > 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.
Well, I'm figuring that most people would use "CREATE NEXT PARTITION" instead.
ALTER TABLE foo ADD PARTITION NEXT;
when a sequence of partitions has been defined
--
Simon Riggs http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
