pgsql: Revert "Stop btree indexscans upon reaching nulls in either dire

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Revert "Stop btree indexscans upon reaching nulls in either dire
Date: 2011-11-02 17:39:00
Message-ID: E1RLemC-0003xs-QF@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Revert "Stop btree indexscans upon reaching nulls in either direction."

This reverts commit ff41611ddcce36b8f87b73c65b78d8f71a157302.
As pointed out by Naoya Anzai, we need to do more work to make that
idea handle end-of-index cases, and it is looking like too much risk
for a back-patch. So bug #6278 is only going to be fixed in HEAD.

Branch
------
REL8_3_STABLE

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

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

Browse pgsql-committers by date

  From Date Subject
Next Message Robert Haas 2011-11-02 18:27:25 Re: [COMMITTERS] pgsql: Reduce checkpoints and WAL traffic on low activity database serv
Previous Message Simon Riggs 2011-11-02 17:16:21 pgsql: Update more comments about checkpoints being done by bgwriter