Re: Seqscan rather than Index

От: Tom Lane
Тема: Re: Seqscan rather than Index
Дата: ,
Msg-id: 26003.1103218313@sss.pgh.pa.us
(см: обсуждение, исходный текст)
Ответ на: Seqscan rather than Index  (Jon Anderson)
Список: pgsql-performance

Скрыть дерево обсуждения

Seqscan rather than Index  (Jon Anderson, )
 Re: Seqscan rather than Index  (Tom Lane, )
 Re: Seqscan rather than Index  (David Brown, )
  Re: Seqscan rather than Index  (Richard Huxton, )
   Re: Seqscan rather than Index  (Greg Stark, )
    Re: Seqscan rather than Index  (Tom Lane, )
     Re: Seqscan rather than Index  (Greg Stark, )
      Re: Seqscan rather than Index  (Tom Lane, )
    Re: Seqscan rather than Index  ("Steinar H. Gunderson", )
     Re: Seqscan rather than Index  ("Steinar H. Gunderson", )
      Re: Seqscan rather than Index  (Frank Wiles, )
       Re: Seqscan rather than Index  ("Steinar H. Gunderson", )
       Re: Seqscan rather than Index  (Tom Lane, )
        Re: Seqscan rather than Index  (Frank Wiles, )
     Re: Seqscan rather than Index  (Bruno Wolff III, )
      Re: Seqscan rather than Index  ("Steinar H. Gunderson", )

Jon Anderson <> writes:
> Any hints on what to do to make PostgreSQL use the index?

You might want to reduce random_page_cost a little.

Keep in mind that your test case is small enough to fit in RAM and is
probably not reflective of what will happen with larger tables.

            regards, tom lane


В списке pgsql-performance по дате сообщения:

От: Tom Lane
Дата:
Сообщение: Re: UNION ALL vs INHERITANCE
От: David Brown
Дата:
Сообщение: Re: Seqscan rather than Index