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
Дата
Msg-id CAA-aLv5zAZsuefLPf__8PFfD3peyB+f=AsuMEAoH8UnWpDuRqA@mail.gmail.com
обсуждение исходный текст
Ответ на Re: pgsql: Consider index-only scans even when there is no matching qual or  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-committers
On 11 October 2011 21:45, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> 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.

Ah okay, understood.

--
Thom Brown
Twitter: @darkixion
IRC (freenode): dark_ixion
Registered Linux user: #516935

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

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

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: pgsql: Consider index-only scans even when there is no matching qual or
Следующее
От: Bruce Momjian
Дата:
Сообщение: pgsql: Document that not backing up postmaster.pid and postmaster.opts