Re: Old-style OR indexscan slated for destruction

Поиск
Список
Период
Сортировка
Искать
От
Christopher Kings-Lynne
Тема
Re: Old-style OR indexscan slated for destruction
Дата
Msg-id
426C5607.2020000@familyhealth.com.au
Ответ на
Список
Дерево обсуждения
Old-style OR indexscan slated for destruction Tom Lane <tgl@sss.pgh.pa.us>
Re: Old-style OR indexscan slated for destruction Oleg Bartunov <oleg@sai.msu.su>
Re: Old-style OR indexscan slated for destruction Christopher Kings-Lynne <chriskl@familyhealth.com.au>
Re: Old-style OR indexscan slated for destruction Tom Lane <tgl@sss.pgh.pa.us>
Re: Old-style OR indexscan slated for destruction Christopher Kings-Lynne <chriskl@familyhealth.com.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

В списке pgsql-hackers по дате отправления
От: Bruce Momjian
Дата:
От: Tom Lane
Дата:
FAQ