Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
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: Mon, 25 Apr 2005 10:29:27 +0800
- Message-id: <426C5607(dot)2020000(at)familyhealth(dot)com(dot)au>
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
- Follow-Ups:
- Re: Old-style OR indexscan slated for destruction
- From: Tom Lane
- Re: Old-style OR indexscan slated for destruction
- References:
- Old-style OR indexscan slated for destruction
- From: Tom Lane
- Re: Old-style OR indexscan slated for destruction
- From: Oleg Bartunov
- Old-style OR indexscan slated for destruction
- Prev by Date: Re: idea for concurrent seqscans
- Next by Date: Re: Old-style OR indexscan slated for destruction
- Previous by thread: Re: Old-style OR indexscan slated for destruction
- Next by thread: Re: Old-style OR indexscan slated for destruction
- Indexes: