| From: | amul sul <sulamul(at)gmail(dot)com> |
|---|---|
| To: | Jeevan Ladhe <jeevan(dot)ladhe(at)enterprisedb(dot)com> |
| Cc: | Ashutosh Bapat <ashutosh(dot)bapat(at)enterprisedb(dot)com>, Beena Emerson <memissemerson(at)gmail(dot)com>, Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp>, Rajkumar Raghuwanshi <rajkumar(dot)raghuwanshi(at)enterprisedb(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Rahila Syed <rahilasyed90(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Adding support for Default partition in partitioning |
| Date: | 2017-06-07 05:59:15 |
| Message-ID: | CAAJ_b97MiAQ2mXH895hXj0q6GR+VR5FVy0f=NR3gEGnt=KvzWg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Jun 7, 2017 at 10:30 AM, Jeevan Ladhe
<jeevan(dot)ladhe(at)enterprisedb(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Munro | 2017-06-07 06:14:25 | Re: PG10 transition tables, wCTEs and multiple operations on the same table |
| Previous Message | Michael Paquier | 2017-06-07 05:39:26 | Re: tap tests on older branches fail if concurrency is used |