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

pgsql: Fix ginint4_queryextract() to actually do what it was intended to

From: tgl(at)postgresql(dot)org (Tom Lane)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Fix ginint4_queryextract() to actually do what it was intended to
Date: 2010-03-25 15:50:22
Message-ID: 20100325155022.3E6BD7541D0@cvs.postgresql.org (view raw or flat)
Thread:
Lists: 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.

Tags:
----
REL8_3_STABLE

Modified Files:
--------------
    pgsql/contrib/intarray:
        _int_gin.c (r1.5 -> r1.5.2.1)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/contrib/intarray/_int_gin.c?r1=1.5&r2=1.5.2.1)

pgsql-committers by date

Next:From: Heikki LinnakangasDate: 2010-03-25 16:52:46
Subject: Re: pgsql: Change replication connection log format to allow for a database
Previous:From: Tom LaneDate: 2010-03-25 15:50:15
Subject: pgsql: Fix ginint4_queryextract() to actually do what it was intended to

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