On Fri, Aug 4, 2017 at 7:48 PM, Robert Haas <robertmh...@gmail.com> wrote: > On Mon, Jul 31, 2017 at 8:28 AM, Beena Emerson <memissemer...@gmail.com> > wrote: > > Why do we need to introduce PARTITION_RANGE_DATUM_DEFAULT at all? It > seems to me that the handling of default range partitions ought to be > similar to the way a null-accepting list partition is handled - > namely, it wouldn't show up in the "datums" or "kind" array at all, > instead just showing up in PartitionBoundInfoData's default_index > field. >
I have updated the patch to make it similar to the way default/null is handled in list partition, removing the PARTITION_RANGE_DATUM_DEFAULT. This is to be applied over v24 patches shared by Jeevan [1] which applies on commit id 5ff3d73813ebcc3ff80be77c30b458d728951036. The RelationBuildPartitionDesc has been modified a lot, especially the way all_bounds, ndatums and rbounds are set. [1] https://www.postgresql.org/message-id/CAOgcT0OVwDu%2BbeChWb5R5s6rfKLCiWcZT5617hqu7T3GdA1hAw%40mail.gmail.com -- Beena Emerson EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
default_range_partition_v9.patch
Description: Binary data
-- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
