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-0003xq-OK@gemulon.postgresql.org
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-committers

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

This reverts commit d23165bbc306005f687756a20d9af807d665a1f2.
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_4_STABLE

Details
-------
http://git.postgresql.org/pg/commitdiff/9f19cc28a439c88c73bc6083ebd9cd603a65b7fe

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