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 20081022125356.32FCD7545A4@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.

Modified Files:
--------------
    pgsql/src/backend/access/gist:
        gistget.c (r1.78 -> r1.79)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/gist/gistget.c?r1=1.78&r2=1.79)
    pgsql/src/include/access:
        gist_private.h (r1.34 -> r1.35)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/include/access/gist_private.h?r1=1.34&r2=1.35)

pgsql-committers by date:

Previous
From: petere@postgresql.org (Peter Eisentraut)
Date:
Subject: pgsql: SQL:2008 alternative syntax for LIMIT/OFFSET: OFFSET num
Next
From: teodor@postgresql.org (Teodor Sigaev)
Date:
Subject: pgsql: Fix GiST's killing tuple: GISTScanOpaque->curpos wasn't