| From: | Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp> |
|---|---|
| To: | Ashutosh Bapat <ashutosh(dot)bapat(at)enterprisedb(dot)com> |
| Cc: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: constraint exclusion and nulls in IN (..) clause |
| Date: | 2018-02-05 04:25:00 |
| Message-ID: | 440dd233-d576-f482-66a3-8a79173b0af2@lab.ntt.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2018/02/05 13:20, Ashutosh Bapat wrote:
> On Thu, Feb 1, 2018 at 2:23 PM, Amit Langote
> <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp> wrote:
>>
>> Yeah, the patch in its current form is wrong, because it will give wrong
>> answers if the operator being used in a SAOP is non-strict. I modified
>> the patch to consider operator strictness before doing anything with nulls.
>
> That's fine, but I am not sure whether this fits constraint
> exclusion's charter. Please add this patch to the next commitfest so
> that we can have a better opinion.
OK, done.
Thanks,
Amit
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Masahiko Sawada | 2018-02-05 04:53:10 | Re: [HACKERS] [PATCH] Vacuum: Update FSM more frequently |
| Previous Message | Ashutosh Bapat | 2018-02-05 04:20:51 | Re: constraint exclusion and nulls in IN (..) clause |