Re: Reduce planning time for large NOT IN lists containing NULL - Mailing list pgsql-hackers

From Zsolt Parragi
Subject Re: Reduce planning time for large NOT IN lists containing NULL
Date
Msg-id CAN4CZFNJHro_pEVTHggBX43f+AebwKLZdp39+V4pV0EB4BZuZw@mail.gmail.com
Whole thread Raw
In response to Re: Reduce planning time for large NOT IN lists containing NULL  (Ilia Evdokimov <ilya.evdokimov@tantorlabs.com>)
Responses Re: Reduce planning time for large NOT IN lists containing NULL
List pgsql-hackers
Hello

I think it would be a good idea to add a test, I think there's a
regression with this patch:

CREATE TABLE notin_test AS SELECT generate_series(1, 1000) AS x;
ANALYZE notin_test;

CREATE FUNCTION replace_elem(arr int[], idx int, val int)
RETURNS int[] AS $$
BEGIN
    arr[idx] := val;
    RETURN arr;
END;
$$ LANGUAGE plpgsql IMMUTABLE;

EXPLAIN SELECT * FROM notin_test WHERE x <> ALL(ARRAY[1,99,3]);
-- same array, constructed from an array with a NULL
EXPLAIN SELECT * FROM notin_test WHERE x <>
ALL(replace_elem(ARRAY[1,NULL,3], 2, 99));
DROP TABLE notin_test;
DROP FUNCTION replace_elem;

ARR_HASNULL probably should be array_contains_nulls, as ARR_HASNULL
simply checks for the existence of a NULL bitmap.



pgsql-hackers by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: Don't synchronously wait for already-in-progress IO in read stream
Next
From: Jacob Champion
Date:
Subject: Re: libpq: Bump protocol version to version 3.2 at least until the first/second beta