Re: select on 1milion register = 6s

От: Jan Dittmer
Тема: Re: select on 1milion register = 6s
Дата: ,
Msg-id: 46B0C4C7.7000202@l4x.org
(см: обсуждение, исходный текст)
Ответ на: Re: select on 1milion register = 6s  ("Scott Marlowe")
Список: pgsql-performance

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

select on 1milion register = 6s  ("Bruno Rodrigues Siqueira", )
 Re: select on 1milion register = 6s  (Craig James, )
  RES: select on 1milion register = 6s  ("Bruno Rodrigues Siqueira", )
   Re: RES: select on 1milion register = 6s  (Ragnar, )
    RES: RES: select on 1milion register = 6s  ("Bruno Rodrigues Siqueira", )
    Re: RES: select on 1milion register = 6s  (Decibel!, )
     RES: RES: select on 1milion register = 6s  ("Bruno Rodrigues Siqueira", )
      Re: RES: RES: select on 1milion register = 6s  (Decibel!, )
     Re: RES: RES: select on 1milion register = 6s  (Decibel!, )
   Re: select on 1milion register = 6s  ("Scott Marlowe", )
    Re: select on 1milion register = 6s  (Alvaro Herrera, )
    Re: select on 1milion register = 6s  (Jan Dittmer, )
 Re: select on 1milion register = 6s  (Hervé Piedvache, )
  RES: select on 1milion register = 6s  ("Bruno Rodrigues Siqueira", )
  RES: select on 1milion register = 6s  ("Bruno Rodrigues Siqueira", )

Scott Marlowe wrote:
>> random_page_cost = 1                    # units are one sequential page
>> fetch
>
> Seldom if ever is it a good idea to bonk the planner on the head with
> random_page_cost=1.  setting it to 1.2 ot 1.4 is low enough, but 1.4
> to 2.0 is more realistic.

Which is probably the reason why the planner thinks a seq scan is
faster than an index scan...

Jan


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

От: "Luke Lonergan"
Дата:
Сообщение: Re: Postgres configuration for 64 CPUs, 128 GB RAM...
От: "Carlos H. Reimer"
Дата:
Сообщение: RES: RES: Improving select peformance