| From: | Ashutosh Bapat <ashutosh(dot)bapat(at)enterprisedb(dot)com> |
|---|---|
| To: | Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp> |
| Cc: | Etsuro Fujita <fujita(dot)etsuro(at)lab(dot)ntt(dot)co(dot)jp>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Oddity in COPY FROM handling of check constraints on partition tables |
| Date: | 2018-03-28 09:51:43 |
| Message-ID: | CAFjFpReWH=JuGL2cGRabADg4PUWF3WRbGE1fAuX6uD8dBXLxOQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Mar 28, 2018 at 6:58 AM, Amit Langote
<Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp> wrote:
>> which violates the constraint on the column b (ie, b > 0), so this
>> should abort. The reason for that is because CopyFrom looks at the
>> parent relation's constraints, not the partition's constraints, when
>> checking the constraint against the input row.
>
> Good catch, thanks!
>
+1
>> Attached is a patch for fixing this issue.
>
> That looks good to me. This one would need to be back-patched to v10.
Thanks. Please add to the next commitfest so that it doesn't get lost.
We can not add this to v11 open items since it isn't a v11 bug
exactly.
--
Best Wishes,
Ashutosh Bapat
EnterpriseDB Corporation
The Postgres Database Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Langote | 2018-03-28 10:30:56 | Re: [HACKERS] path toward faster partition pruning |
| Previous Message | Amit Langote | 2018-03-28 09:29:26 | Re: [HACKERS] path toward faster partition pruning |