Re: seq scan over 3.3 million rows instead of single keyindex access

От: Andrus
Тема: Re: seq scan over 3.3 million rows instead of single keyindex access
Дата: ,
Msg-id: ggbhs5$b6f$1@news.hub.org
(см: обсуждение, исходный текст)
Ответ на: Re: seq scan over 3.3 million rows instead of single key index access  (Andreas Kretschmer)
Список: pgsql-performance

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

seq scan over 3.3 million rows instead of single key index access  ("Andrus", )
 Re: seq scan over 3.3 million rows instead of single key index access  (Gregory Stark, )
  Re: seq scan over 3.3 million rows instead of single key index access  (Tom Lane, )
  Re: seq scan over 3.3 million rows instead of single key index access  ("Andrus", )
   Re: seq scan over 3.3 million rows instead of single key index access  ("A. Kretschmer", )
 Re: seq scan over 3.3 million rows instead of single key index access  (Andreas Kretschmer, )
  Re: seq scan over 3.3 million rows instead of single keyindex access  ("Andrus", )
 Re: seq scan over 3.3 million rows instead of single key index access  (Andreas Kretschmer, )

> An index-scan makes only sense if rid contains considerable more than
> 3000000 rows.

I'm sorry, I meant using index to get the row.

Andrus.



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

От: "Andrus"
Дата:
Сообщение: Re: Hash join on int takes 8..114 seconds
От: Tomas Vondra
Дата:
Сообщение: Re: Hash join on int takes 8..114 seconds