Re: Old-style OR indexscan slated for destruction - Mailing list pgsql-hackers

From Christopher Kings-Lynne
Subject Re: Old-style OR indexscan slated for destruction
Date
Msg-id 426C5607.2020000@familyhealth.com.au
Whole thread Raw
In response to Re: Old-style OR indexscan slated for destruction  (Oleg Bartunov <oleg@sai.msu.su>)
Responses Re: Old-style OR indexscan slated for destruction
List pgsql-hackers
>> I am about to rip out the code that supports multiple indexscans for OR
>> conditions inside a single IndexScan plan node.  As best I can tell,
>> the new-style bitmap-OR code is as fast or faster than the old way
>> even in fully cached test cases (ie, with no allowance for improved
>> efficiency of disk access).  So there's no percentage in maintaining
>> support for the old way, and getting rid of it will allow simplification
>> of code and data structures in the planner.

For all index types?  Even lossy ones?

Chris


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: idea for concurrent seqscans
Next
From: Tom Lane
Date:
Subject: Re: Old-style OR indexscan slated for destruction