| From: | David Rowley <dgrowleyml(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Peter Geoghegan <pg(at)bowt(dot)ie>, James Coleman <jtc331(at)gmail(dot)com>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Binary search in ScalarArrayOpExpr for OR'd constant arrays |
| Date: | 2021-04-12 23:49:08 |
| Message-ID: | CAApHDvqTKS2HJuEPwDjc3NRJQZJ1-90O3V=ygQVSS1g1=Dg87g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, 13 Apr 2021 at 11:42, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> David Rowley <dgrowleyml(at)gmail(dot)com> writes:
> > I realised when working on something unrelated last night that we can
> > also do hash lookups for NOT IN too.
>
> ... and still get the behavior right for nulls?
Yeah, it will. There are already some special cases for NULLs in the
IN version. Those would need to be adapted for NOT IN.
David
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2021-04-12 23:52:44 | Re: Teaching users how they can get the most out of HOT in Postgres 14 |
| Previous Message | Tom Lane | 2021-04-12 23:42:03 | Re: Binary search in ScalarArrayOpExpr for OR'd constant arrays |