Re: [HACKERS] BRIN cost estimate

Поиск
Список
Период
Сортировка
От Alvaro Herrera
Тема Re: [HACKERS] BRIN cost estimate
Дата
Msg-id 20170406214748.3jhqwipgkbmj5pl4@alvherre.pgsql
обсуждение исходный текст
Ответ на Re: [HACKERS] BRIN cost estimate  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-hackers
Tom Lane wrote:

> TBH, I think that code is in the noise.  It doesn't involve any disk
> access, or catalog access, or user-defined function calls.  I wouldn't
> bother trying to account for it.

I removed it in the pushed version.

> What you should be accounting for is the ensuing heap page accesses,
> but I assume that's done somewhere else.

It's supposed to be accounted for, yeah.

One thing we do not account for is the number of extra heap accesses we
do for unsummarized ranges (mostly, heap has grown but the index doesn't
cover the new pages yet).

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



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

Предыдущее
От: David Steele
Дата:
Сообщение: Re: [HACKERS] increasing the default WAL segment size
Следующее
От: Andres Freund
Дата:
Сообщение: Re: [HACKERS] tuplesort_gettuple_common() and *should_free argument