AW: [HACKERS] Caution: tonight's commits force initdb

Поиск
Список
Период
Сортировка
От Zeugswetter Andreas IZ5
Тема AW: [HACKERS] Caution: tonight's commits force initdb
Дата
Msg-id 219F68D65015D011A8E000006F8590C60339E0A6@sdexcsrv1.f000.d0188.sd.spardat.at
обсуждение исходный текст
Ответы RE: [HACKERS] Caution: tonight's commits force initdb  ("Hiroshi Inoue" <Inoue@tpf.co.jp>)
Список pgsql-hackers
> Hmm,Index scan is chosen to select all rows.
> AFAIK,sequential scan + sort is much faster than index scan in
> most cases.
> 
>     cost of index scan < cost of sequential scan + cost of sort
> 
This is usually true. It might need resources though that are not available,
e.g. 8 GB sort space. It also depends on whether the application is
interested in
first row (interactive), or all row performance (batch). Other DB's can
switch modes 
to decide on the wanted behavior. So I think there is no yes/no decision on
this.

Andreas


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

Предыдущее
От: "Ansley, Michael"
Дата:
Сообщение: Lex and things...
Следующее
От: "Hiroshi Inoue"
Дата:
Сообщение: RE: [HACKERS] Caution: tonight's commits force initdb