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

pgsql: Fix oversight in handling of row-comparison index keys: if the

From: tgl(at)postgresql(dot)org (Tom Lane)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Fix oversight in handling of row-comparison index keys: if the
Date: 2007-01-07 01:56:24
Message-ID: 20070107015624.A92A09FB1EB@postgresql.org (view raw or flat)
Thread:
Lists: pgsql-committers
Log Message:
-----------
Fix oversight in handling of row-comparison index keys: if the row comparison
doesn't exactly match the index, we may have to change our initial positioning
strategy.  For example, given an index on (f1,f2,f3) and a WHERE condition
"ROW(f1,f3) > ROW(2,3)", the code extracted the initial-positioning condition
"f1 > 2", which is wrong ... it has to be "f1 >= 2", else some rows matching
the WHERE condition may fail to be returned.

Applying patch to 8.2 only --- I'll fix it in HEAD later as part of the
planned index improvements (reverse-sort and NULLS FIRST/LAST work).

Tags:
----
REL8_2_STABLE

Modified Files:
--------------
    pgsql/src/backend/access/nbtree:
        nbtsearch.c (r1.107 -> r1.107.2.1)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/nbtree/nbtsearch.c.diff?r1=1.107&r2=1.107.2.1)

pgsql-committers by date

Next:From: Tom LaneDate: 2007-01-07 03:00:12
Subject: Re: [COMMITTERS] pgsql: Check for ERANGE in exp()
Previous:From: Peter EisentrautDate: 2007-01-07 00:13:55
Subject: pgsql: Allow XML fragment to contain a XML declaration.

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