diff options
| author | David Rowley <drowley@postgresql.org> | 2021-07-07 16:29:17 +1200 |
|---|---|---|
| committer | David Rowley <drowley@postgresql.org> | 2021-07-07 16:29:17 +1200 |
| commit | 29f45e299e7ffa1df0db44b8452228625479487f (patch) | |
| tree | 948f286a1db23d164aeb20d4cb3d172ed986e758 /contrib/postgres_fdw/postgres_fdw.c | |
| parent | d854720df6df68cfe1432342e33c9e3020572a51 (diff) | |
| download | postgresql-29f45e299e7ffa1df0db44b8452228625479487f.tar.gz postgresql-29f45e299e7ffa1df0db44b8452228625479487f.zip | |
Use a hash table to speed up NOT IN(values)
Similar to 50e17ad28, which allowed hash tables to be used for IN clauses
with a set of constants, here we add the same feature for NOT IN clauses.
NOT IN evaluates the same as: WHERE a <> v1 AND a <> v2 AND a <> v3.
Obviously, if we're using a hash table we must be exactly equivalent to
that and return the same result taking into account that either side of
the condition could contain a NULL. This requires a little bit of
special handling to make work with the hash table version.
When processing NOT IN, the ScalarArrayOpExpr's operator will be the <>
operator. To be able to build and lookup a hash table we must use the
<>'s negator operator. The planner checks if that exists and is hashable
and sets the relevant fields in ScalarArrayOpExpr to instruct the executor
to use hashing.
Author: David Rowley, James Coleman
Reviewed-by: James Coleman, Zhihong Yu
Discussion: https://postgr.es/m/CAApHDvoF1mum_FRk6D621edcB6KSHBi2+GAgWmioj5AhOu2vwQ@mail.gmail.com
Diffstat (limited to 'contrib/postgres_fdw/postgres_fdw.c')
0 files changed, 0 insertions, 0 deletions