Re: [HACKERS] Queuing all tables for analyze after recovery

Поиск
Список
Период
Сортировка
От Vik Fearing
Тема Re: [HACKERS] Queuing all tables for analyze after recovery
Дата
Msg-id ce573620-f1cb-ffc9-fcb0-68ff76226196@2ndquadrant.com
обсуждение исходный текст
Ответ на Re: [HACKERS] Queuing all tables for analyze after recovery  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-hackers
On 10/19/2017 11:26 PM, Tom Lane wrote:
> Vik Fearing <vik.fearing@2ndquadrant.com> writes:
>> On 10/19/2017 10:54 PM, Tom Lane wrote:
>>> Uh ... recommended by whom?  pg_statistic has exactly the same reliability
>>> guarantees as the rest of the system catalogs.
> 
>> For data statistics, sure.  One thing I'm unhappy about is that
>> pg_stat_all_tables is blank.
> 
> Well, that's because we throw away the stats collector's stats after a
> crash -- or, in the failover case, because the promoted slave has its own
> counters and not the master's.  ANALYZE isn't going to help that at all.

Sure it will.  ANALYZE estimates n_dead_tup, which often accurate enough
for autovacuum to figure out what to do.
-- 
Vik Fearing                                          +33 6 46 75 15 36
http://2ndQuadrant.fr     PostgreSQL : Expertise, Formation et Support


-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

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

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: [HACKERS] Queuing all tables for analyze after recovery
Следующее
От: Tomas Vondra
Дата:
Сообщение: [HACKERS] CUBE seems a bit confused about ORDER BY