| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
| Cc: | Oleg Bartunov <oleg(at)sai(dot)msu(dot)su>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Old-style OR indexscan slated for destruction |
| Date: | 2005-04-25 02:45:31 |
| Message-ID: | 3100.1114397131@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> writes:
> 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?
Can't see that a lossy index would make any difference ...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christopher Kings-Lynne | 2005-04-25 02:47:14 | Re: Old-style OR indexscan slated for destruction |
| Previous Message | Christopher Kings-Lynne | 2005-04-25 02:29:27 | Re: Old-style OR indexscan slated for destruction |