Re: Old-style OR indexscan slated for destruction
| От | Tom Lane |
|---|---|
| Тема | Re: Old-style OR indexscan slated for destruction |
| Дата | |
| Msg-id | 3100.1114397131@sss.pgh.pa.us обсуждение |
| Ответ на | Re: Old-style OR indexscan slated for destruction (Christopher Kings-Lynne <chriskl@familyhealth.com.au>) |
| Ответы |
Re: Old-style OR indexscan slated for destruction
|
| Список | pgsql-hackers |
Christopher Kings-Lynne <chriskl@familyhealth.com.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
В списке pgsql-hackers по дате отправления: