Re: BUG #15830: index pg_stat_all_indexes.idx_tup_read statistic error?

Поиск
Список
Период
Сортировка
От Peter Geoghegan
Тема Re: BUG #15830: index pg_stat_all_indexes.idx_tup_read statistic error?
Дата
Msg-id CAH2-WzkKNOO6YqOVvh80rt-4ZuU_pHZ1XitOeMn212jVQXyqvA@mail.gmail.com
обсуждение исходный текст
Ответ на BUG #15830: index pg_stat_all_indexes.idx_tup_read statistic error?  (PG Bug reporting form <noreply@postgresql.org>)
Список pgsql-bugs
On Sat, Jun 1, 2019 at 12:01 AM PG Bug reporting form
<noreply@postgresql.org> wrote:
> The question is, does INDEX SCAN clean up the garbage version of leaf page?
> Or it's a bug?

Yes, sometimes that happens -- the kill_prior_tuple optimization can
kick in, even with a simple SELECT.

It would be clearer what was going on if you forced a bitmap index
scan (e.g. "set enable_indexscan=off;"). That way, the EXPLAIN
(ANALYZE, BUFFERS) instrumentation will show heap blocks and index
blocks separately.

-- 
Peter Geoghegan



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

Предыдущее
От: PG Bug reporting form
Дата:
Сообщение: BUG #15830: index pg_stat_all_indexes.idx_tup_read statistic error?
Следующее
От: Robert Vollmert
Дата:
Сообщение: Re: inconsistent behaviour of json_to_record and friends withembedded json