Restore correct btree preprocessing of "indexedcol IS NULL" conditions.
Such a condition is unsatisfiable in combination with any other type of
btree-indexable condition (since we assume btree operators are always
strict). 8.3 and 8.4 had an explicit test for this, which I removed in
commit 29c4ad98293e3c5cb3fcdd413a3f4904efff8762, mistakenly thinking that
the case would be subsumed by the more general handling of IS (NOT) NULL
added in that patch. Put it back, and improve the comments about it, and
add a regression test case.
Per bug #6079 from Renat Nasyrov, and analysis by Dean Rasheed.
Branch
------
REL9_1_STABLE
Details
-------
http://git.postgresql.org/pg/commitdiff/3b80219e96f2d2b696ed8dc395d468b38d8ef592
Modified Files
--------------
src/backend/access/nbtree/nbtutils.c | 17 +++++++++-
src/test/regress/expected/create_index.out | 48 ++++++++++++++++++++++++++++
src/test/regress/sql/create_index.sql | 8 +++++
3 files changed, 71 insertions(+), 2 deletions(-)
