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-0006pN-73@gemulon.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
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
------
REL9_1_STABLE
Details
-------
http://git.postgresql.org/pg/commitdiff/048fffed55ff1d6d346130e4a6b7be434e81e82c
Modified Files
--------------
src/backend/access/nbtree/nbtutils.c | 107 +++++++++++++--------------------
1 files changed, 42 insertions(+), 65 deletions(-)
From | Date | Subject | |
---|---|---|---|
Next Message | User Mhasegawa | 2011-11-01 05:29:46 | pgbulkload - pgbulkload: Support PostgreSQL 9.1 |
Previous Message | User Hinoue | 2011-10-31 14:20:20 | psqlodbc - psqlodbc: Fix the bug that PostgreSQL's function calls in |