Re: Old-style OR indexscan slated for destruction

From: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>
To: Oleg Bartunov <oleg(at)sai(dot)msu(dot)su>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Old-style OR indexscan slated for destruction
Date: 2005-04-25 02:29:27
Message-ID: 426C5607.2020000@familyhealth.com.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2005-04-25 02:45:31 Re: Old-style OR indexscan slated for destruction
Previous Message Bruce Momjian 2005-04-25 01:45:17 Re: idea for concurrent seqscans