pgsql: Fix ginint4_queryextract() to actually do what it was intended to - Mailing list pgsql-committers

From tgl@postgresql.org (Tom Lane)
Subject pgsql: Fix ginint4_queryextract() to actually do what it was intended to
Date
Msg-id 20100325155010.DC3297541D0@cvs.postgresql.org
Whole thread Raw
List pgsql-committers
Log Message:
-----------
Fix ginint4_queryextract() to actually do what it was intended to do for an
unsatisfiable query, such as indexcol && empty_array.  It should return -1
to tell GIN no scan is required; but silly typo disabled the logic for that,
resulting in unnecessary "GIN indexes do not support whole-index scans" error.
Per bug report from Jeff Trout.

Back-patch to 8.3 where the logic was introduced.

Modified Files:
--------------
    pgsql/contrib/intarray:
        _int_gin.c (r1.10 -> r1.11)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/contrib/intarray/_int_gin.c?r1=1.10&r2=1.11)

pgsql-committers by date:

Previous
From: alvherre@postgresql.org (Alvaro Herrera)
Date:
Subject: pgsql: Prevent ALTER USER f RESET ALL from removing the settings that
Next
From: tgl@postgresql.org (Tom Lane)
Date:
Subject: pgsql: Fix ginint4_queryextract() to actually do what it was intended to