Re: index prefetching

Поиск
Список
Период
Сортировка
От Konstantin Knizhnik
Тема Re: index prefetching
Дата
Msg-id 316ca3df-d1b0-49ce-ba05-56b342b4cefa@garret.ru
обсуждение исходный текст
Ответ на Re: index prefetching  (Tomas Vondra <tomas.vondra@enterprisedb.com>)
Ответы Re: index prefetching  (Tomas Vondra <tomas.vondra@enterprisedb.com>)
Список pgsql-hackers


On 22/01/2024 1:47 am, Tomas Vondra wrote:
h, right. Well, you're right in this case we perhaps could set just one
of those flags, but the "purpose" of the two places is quite different.

The "prefetch" flag is fully controlled by the prefetcher, and it's up
to it to change it (e.g. I can easily imagine some new logic touching
setting it to "false" for some reason).

The "data" flag is fully controlled by the custom callbacks, so whatever
the callback stores, will be there.

I don't think it's worth simplifying this. In particular, I don't think
the callback can assume it can rely on the "prefetch" flag.

Why not to add "all_visible" flag to IndexPrefetchEntry ? If will not cause any extra space overhead (because of alignment), but allows to avoid dynamic memory allocation (not sure if it is critical, but nice to avoid if possible).


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

Предыдущее
От: Peter Smith
Дата:
Сообщение: Re: pg_stat_statements and "IN" conditions
Следующее
От: Peter Smith
Дата:
Сообщение: Re: Things I don't like about \du's "Attributes" column