Skip site navigation (1) Skip section navigation (2)

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

From: teodor(at)postgresql(dot)org (Teodor Sigaev)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Fix GiST's killing tuple: GISTScanOpaque->curpos wasn't
Date: 2008-10-22 12:53:56
Message-ID: 20081022125356.32FCD7545A4@cvs.postgresql.org (view raw or flat)
Thread:
Lists: 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

Next:From: Teodor SigaevDate: 2008-10-22 12:54:25
Subject: pgsql: Fix GiST's killing tuple: GISTScanOpaque->curpos wasn't
Previous:From: Peter EisentrautDate: 2008-10-22 11:00:34
Subject: pgsql: SQL:2008 alternative syntax for LIMIT/OFFSET: OFFSET num

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group