Re: [HACKERS] Adding support for Default partition in partitioning - Mailing list pgsql-hackers

From amul sul
Subject Re: [HACKERS] Adding support for Default partition in partitioning
Date
Msg-id CAAJ_b97MiAQ2mXH895hXj0q6GR+VR5FVy0f=NR3gEGnt=KvzWg@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] Adding support for Default partition in partitioning  (Jeevan Ladhe <jeevan.ladhe@enterprisedb.com>)
Responses Re: [HACKERS] Adding support for Default partition in partitioning  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
On Wed, Jun 7, 2017 at 10:30 AM, Jeevan Ladhe
<jeevan.ladhe@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



pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: [HACKERS] tap tests on older branches fail if concurrency is used
Next
From: Thomas Munro
Date:
Subject: Re: [HACKERS] PG10 transition tables, wCTEs and multiple operationson the same table