]> granicus.if.org Git - postgresql/commit
projects / postgresql / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: e034e51) | patch
During repeated rescan of GiST index it's possible that scan key
authorTeodor Sigaev <teodor@sigaev.ru>
Fri, 17 Oct 2008 17:02:21 +0000 (17:02 +0000)
committerTeodor Sigaev <teodor@sigaev.ru>
Fri, 17 Oct 2008 17:02:21 +0000 (17:02 +0000)
commitbeeb3562dd5194bf47f8f06565f4b54b181eb64b
tree472a814c4cc946da5f0761ab1cb7530131520641tree | snapshot
parente034e517a70265a2e7f9552d2a9fd33102d21896commit | diff
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 diff | blob | history
src/backend/access/gist/gistscan.c diff | blob | history
src/include/access/gist_private.h diff | blob | history
Unnamed repository; edit this file 'description' to name the repository.