database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-09-02 04:21:28 +03:00
Code Activity

Revert buggy optimization of index scans

Browse Source 
606c0123d6 attempted to reduce cost of index scans using > and <
strategies, though got that completely wrong in a few complex cases.

Revert whole patch until we find a safe optimization.
This commit is contained in:
Simon Riggs
2016-03-03 09:53:43 +00:00
parent 6c90996a4c
commit c7111d11b1
3 changed files with 0 additions and 35 deletions
Download Patch File Download Diff File Expand all files Collapse all files

27
src/backend/access/nbtree/nbtsearch.c
View File

@@ -1026,33 +1026,6 @@ _bt_first(IndexScanDesc scan, ScanDirection dir)
if (goback)
offnum = OffsetNumberPrev(offnum);
/*
* By here the scan position is now set for the first key. If all further
* tuples are expected to match we set the SK_BT_MATCHED flag to avoid
* re-checking the scan key later. This is a big win for slow key matches
* though is still significant even for fast datatypes.
*/
switch (startKeys[0]->sk_strategy)
{
case BTEqualStrategyNumber:
break;
case BTGreaterEqualStrategyNumber:
case BTGreaterStrategyNumber:
if (ScanDirectionIsForward(dir))
startKeys[0]->sk_flags |= SK_BT_MATCHED;
break;
case BTLessEqualStrategyNumber:
case BTLessStrategyNumber:
if (ScanDirectionIsBackward(dir))
startKeys[0]->sk_flags |= SK_BT_MATCHED;
break;
default:
break;
}
/* remember which buffer we have pinned, if any */
Assert(!BTScanPosIsValid(so->currPos));
so->currPos.buf = buf;

7
src/backend/access/nbtree/nbtutils.c
View File

@@ -1429,13 +1429,6 @@ _bt_checkkeys(IndexScanDesc scan,
bool isNull;
Datum test;
/*
* If the scan key has already matched we can skip this key, as long
* as the index tuple does not contain NULL values.
*/
if (key->sk_flags & SK_BT_MATCHED && !IndexTupleHasNulls(tuple))
continue;
/* row-comparison keys need special processing */
if (key->sk_flags & SK_ROW_HEADER)
{