On Wed, Jun 7, 2017 at 10:30 AM, Jeevan Ladhe <jeevan.la...@enterprisedb.com> wrote: > > >> IIUC, default partition constraints is simply NOT IN (<values of all >> other sibling partitions>). >> If constraint on the default partition refutes the new partition's >> constraints that means we have overlapping partition, and perhaps >> error. > > > You are correct Amul, but this error will be thrown before we try to > check for the default partition data. So, in such cases I think we really > do not need to have logic to check if default partition refutes the new > partition contraints. >
But Ashutosh's suggestion make sense, we might have constraints other than that partitioning constraint on default partition. If those constraints refutes the new partition's constraints, we should skip the scan. Regards, Amul -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
