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

pgsql: Stop btree indexscans upon reaching nulls in either direction.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Stop btree indexscans upon reaching nulls in either direction.
Date: 2011-10-31 20:41:03
Message-ID: E1RKyfH-0006pR-AW@gemulon.postgresql.org (view raw or flat)
Thread:
Lists: pgsql-committers
Stop btree indexscans upon reaching nulls in either direction.

The existing scan-direction-sensitive tests were overly complex, and
failed to stop the scan in cases where it's perfectly legitimate to do so.
Per bug #6278 from Maksym Boguk.

Back-patch to 8.3, which is as far back as the patch applies easily.
Doesn't seem worth sweating over a relatively minor performance issue in
8.2 at this late date.  (But note that this was a performance regression
from 8.1 and before, so 8.2 is being left as an outlier.)

Branch
------
REL8_4_STABLE

Details
-------
http://git.postgresql.org/pg/commitdiff/d23165bbc306005f687756a20d9af807d665a1f2

Modified Files
--------------
src/backend/access/nbtree/nbtutils.c |  107 +++++++++++++--------------------
1 files changed, 42 insertions(+), 65 deletions(-)

pgsql-committers by date

Next:From: User MhasegawaDate: 2011-11-01 05:29:46
Subject: pgbulkload - pgbulkload: Support PostgreSQL 9.1
Previous:From: User HinoueDate: 2011-10-31 14:20:20
Subject: psqlodbc - psqlodbc: Fix the bug that PostgreSQL's function calls in

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