Re: [HACKERS] VACUUM and ANALYZE disagreeing on what reltuples means

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: [HACKERS] VACUUM and ANALYZE disagreeing on what reltuples means
Дата
Msg-id 14503.1521739732@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: [HACKERS] VACUUM and ANALYZE disagreeing on what reltuples means  (Tomas Vondra <tomas.vondra@2ndquadrant.com>)
Ответы Re: [HACKERS] VACUUM and ANALYZE disagreeing on what reltuples means
Re: [patch] BUG #15005: ANALYZE can make pg_class.reltuplesinaccurate.
Список pgsql-hackers
Tomas Vondra <tomas.vondra@2ndquadrant.com> writes:
> 0001 fixes this by tracking the number of actually indexed rows in the
> build states, just like in the other index AMs.
> A VACUUM or ANALYZE will fix the estimate, of course, but for tables
> that are not changing very much it may take quite a while. So I think
> this is something we definitely need to back-patch.

Agreed, and done.  I noticed a second bug in contrib/bloom, too: it'd
forget to write out the last index page if that contained only one
tuple, because the new-page code path in bloomBuildCallback failed to
increment the "count" field after clearing it.

> The 0002 part is the main part, unifying the definition of reltuples on
> three main places:

On to this part ...

            regards, tom lane


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

Предыдущее
От: Robert Haas
Дата:
Сообщение: Re: Updating parallel.sgml's treatment of parallel joins
Следующее
От: Robert Haas
Дата:
Сообщение: Re: Changing default value of wal_sync_method to open_datasync on Linux