From: | teodor(at)postgresql(dot)org (Teodor Sigaev) |
---|---|
To: | pgsql-committers(at)postgresql(dot)org |
Subject: | pgsql: During repeated rescan of GiST index it's possible that scan key |
Date: | 2008-10-17 17:02:21 |
Message-ID: | 20081017170222.006087545A4@cvs.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
Log Message:
-----------
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.
Modified Files:
--------------
pgsql/src/backend/access/gist:
gistget.c (r1.75 -> r1.76)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/gist/gistget.c?r1=1.75&r2=1.76)
gistscan.c (r1.71 -> r1.72)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/gist/gistscan.c?r1=1.71&r2=1.72)
pgsql/src/include/access:
gist_private.h (r1.32 -> r1.33)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/include/access/gist_private.h?r1=1.32&r2=1.33)
From | Date | Subject | |
---|---|---|---|
Next Message | Teodor Sigaev | 2008-10-17 17:02:42 | pgsql: During repeated rescan of GiST index it's possible that scan key |
Previous Message | Neil Conway | 2008-10-16 19:26:01 | pgsql: Fix a small memory leak in ExecReScanAgg() in the hashed |