| From: | Peter Geoghegan <pg(at)heroku(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | "Jonathan S(dot) Katz" <jonathan(dot)katz(at)excoventures(dot)com>, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: IS NOT DISTINCT FROM + Indexing |
| Date: | 2014-07-22 00:02:25 |
| Message-ID: | CAM3SWZQrrdTZ-BR9L+rS5ZAxz7_x0Ysijwvc+vj46bLrtK1f+Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Jul 21, 2014 at 4:57 PM, Andres Freund <andres(at)anarazel(dot)de> wrote:
> I rather doubt it will. x in (y1, ... yn) is essentially expanded to x =
> y1 OR x = y2, ... OR x = yn. I.e. the NULL comparison will be done using
> normal equality comparison and thus not return a row with a NULL
> orderid. Am I missing something?
I was a little bit incautious in my use of words. The point is that a
scanKey could easily represent a ScalarArrayOpExpr with NULLs and
non-NULLs.
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | MauMau | 2014-07-22 01:09:04 | Re: [bug fix] Suppress "autovacuum: found orphan temp table" message |
| Previous Message | Andres Freund | 2014-07-21 23:57:15 | Re: IS NOT DISTINCT FROM + Indexing |