]> granicus.if.org Git - postgresql/commit
During repeated rescan of GiST index it's possible that scan key
authorTeodor Sigaev <teodor@sigaev.ru>
Fri, 17 Oct 2008 17:02:42 +0000 (17:02 +0000)
committerTeodor Sigaev <teodor@sigaev.ru>
Fri, 17 Oct 2008 17:02:42 +0000 (17:02 +0000)
commit2cae6fe7179c49197f22dec7292095764c4e9eaa
treec5b7c12497955a97d721ea2e0935941634bd9fd2
parent6a6f47d00a7505e1b5d562321386253133e05367
During repeated rescan of GiST index it's possible that scan key
is NULL but SK_SEARCHNULL is not set. Add checking IS NULL of keys
to set during key initialization. If key is NULL and SK_SEARCHNULL is not
set then nothnig can be satisfied.
With assert-enabled compilation that causes coredump.

Bug was introduced in 8.3 by support of IS NULL index scan.
src/backend/access/gist/gistget.c
src/backend/access/gist/gistscan.c
src/include/access/gist_private.h