Re: Refactoring the API for amgetmulti

Поиск
Список
Период
Сортировка
Искать
От
Tom Lane
Тема
Re: Refactoring the API for amgetmulti
Дата
Msg-id
3174.1153929592@sss.pgh.pa.us
Ответ на
Список
Дерево обсуждения
Refactoring the API for amgetmulti Tom Lane <tgl@sss.pgh.pa.us>
Re: Refactoring the API for amgetmulti Simon Riggs <simon@2ndquadrant.com>
Re: Refactoring the API for amgetmulti Martijn van Oosterhout <kleptog@svana.org>
Re: Refactoring the API for amgetmulti Tom Lane <tgl@sss.pgh.pa.us>
Re: Refactoring the API for amgetmulti Martijn van Oosterhout <kleptog@svana.org>
Re: Refactoring the API for amgetmulti Tom Lane <tgl@sss.pgh.pa.us>
Martijn van Oosterhout  writes:
> I've considered whether it's worthwhile going to other way: getting the
> IndexScan executer node to uses getmulti to reduce index AM overhead.
> But that requires backward scan support also...

I think Heikki got most of the low-hanging fruit already with that patch
for page-at-a-time scanning in btree.  There's some wasted overhead just
from multiple levels of function call, but I doubt it's really a big
deal anymore.
		regards, tom lane

В списке pgsql-hackers по дате отправления
От: Martijn van Oosterhout
Дата:
От: Bort, Paul
Дата:
FAQ