From: | Vik Fearing <vik(dot)fearing(at)2ndquadrant(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Tomasz Ostrowski <tometzky+pg(at)ato(dot)waw(dot)pl>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Queuing all tables for analyze after recovery |
Date: | 2017-10-19 21:30:13 |
Message-ID: | ce573620-f1cb-ffc9-fcb0-68ff76226196@2ndquadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 10/19/2017 11:26 PM, Tom Lane wrote:
> Vik Fearing <vik(dot)fearing(at)2ndquadrant(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Tomas Vondra | 2017-10-19 21:52:34 | CUBE seems a bit confused about ORDER BY |
Previous Message | Tom Lane | 2017-10-19 21:26:57 | Re: Queuing all tables for analyze after recovery |