Re: pgsql: Consider index-only scans even when there is no matching qual or

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: pgsql: Consider index-only scans even when there is no matching qual or
Дата
Msg-id 3529.1318365938@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: pgsql: Consider index-only scans even when there is no matching qual or  (Thom Brown <thom@linux.com>)
Ответы Re: pgsql: Consider index-only scans even when there is no matching qual or
Список pgsql-committers
Thom Brown <thom@linux.com> writes:
> So an index-only scan is 30 times slower in this particular test case.

Don't see why you'd find that unexpected.  If you have to visit all the
rows, a seqscan is usually going to be the best way.  An indexscan only
has a chance of winning when the index is much smaller than the table,
which isn't the case in your example, even if you hadn't seen to it that
the index wasn't particularly nicely physically ordered.

            regards, tom lane

В списке pgsql-committers по дате отправления:

Предыдущее
От: Thom Brown
Дата:
Сообщение: Re: pgsql: Consider index-only scans even when there is no matching qual or
Следующее
От: Thom Brown
Дата:
Сообщение: Re: pgsql: Consider index-only scans even when there is no matching qual or