pgsql: Fix GiST's killing tuple: GISTScanOpaque->curpos wasn't - Mailing list pgsql-committers

From teodor@postgresql.org (Teodor Sigaev)
Subject pgsql: Fix GiST's killing tuple: GISTScanOpaque->curpos wasn't
Date
Msg-id 20081022125625.655187545A4@cvs.postgresql.org
Whole thread Raw
List pgsql-committers
Log Message:
-----------
Fix GiST's killing tuple: GISTScanOpaque->curpos wasn't
correctly set. As result, killtuple() marks as dead
wrong tuple on page. Bug was introduced by me while fixing
possible duplicates during GiST index scan.

Tags:
----
REL8_1_STABLE

Modified Files:
--------------
    pgsql/src/backend/access/gist:
        gistget.c (r1.52.2.2 -> r1.52.2.3)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/gist/gistget.c?r1=1.52.2.2&r2=1.52.2.3)
        gistscan.c (r1.61.2.1 -> r1.61.2.2)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/gist/gistscan.c?r1=1.61.2.1&r2=1.61.2.2)
    pgsql/src/include/access:
        gist_private.h (r1.8.2.1 -> r1.8.2.2)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/include/access/gist_private.h?r1=1.8.2.1&r2=1.8.2.2)

pgsql-committers by date:

Previous
From: teodor@postgresql.org (Teodor Sigaev)
Date:
Subject: pgsql: Fix GiST's killing tuple: GISTScanOpaque->curpos wasn't
Next
From: tgl@postgresql.org (Tom Lane)
Date:
Subject: pgsql: Dept of better ideas: refrain from creating the planner's