mirror of
https://github.com/postgres/postgres.git
synced 2025-06-19 04:21:08 +03:00
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.
This commit is contained in:
@ -8,7 +8,7 @@
|
||||
* Portions Copyright (c) 1994, Regents of the University of California
|
||||
*
|
||||
* IDENTIFICATION
|
||||
* $PostgreSQL: pgsql/src/backend/access/gist/gistget.c,v 1.75 2008/08/23 10:37:24 teodor Exp $
|
||||
* $PostgreSQL: pgsql/src/backend/access/gist/gistget.c,v 1.76 2008/10/17 17:02:21 teodor Exp $
|
||||
*
|
||||
*-------------------------------------------------------------------------
|
||||
*/
|
||||
@ -134,6 +134,9 @@ gistnext(IndexScanDesc scan, ScanDirection dir, TIDBitmap *tbm)
|
||||
|
||||
so = (GISTScanOpaque) scan->opaque;
|
||||
|
||||
if ( so->qual_ok == false )
|
||||
return 0;
|
||||
|
||||
if (ItemPointerIsValid(&so->curpos) == false)
|
||||
{
|
||||
/* Being asked to fetch the first entry, so start at the root */
|
||||
|
Reference in New Issue
Block a user