| From: | "Euler Taveira" <euler(at)eulerto(dot)com> |
|---|---|
| To: | "nikolai(dot)berkoff" <nikolai(dot)berkoff(at)pm(dot)me>, "pgsql-docs(at)lists(dot)postgresql(dot)org" <pgsql-docs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: vacuumdb --analyze-in-stages |
| Date: | 2021-10-18 18:12:34 |
| Message-ID: | c34d7d46-ef28-4fd2-84bb-7d38b039aae9@www.fastmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
On Fri, Oct 8, 2021, at 6:33 AM, nikolai.berkoff wrote:
> Running --analyze-in-stages on a database with statistics causes the statistics to become significantly worse before they are improved. This could be made clearer in the documentation.
I think the paragraph you modified *already* stated that usefulness of
--analyze-in-stages (newly populated from a restored dump or by pg_upgrade). I
don't think your change is an improvement for --analyze-in-stages description.
If you read the previous paragraph, it explains _how_ (3 stages of ANALYZE with
different settings) and _why_ (produce usable statistics faster).
--
Euler Taveira
EDB https://www.enterprisedb.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Euler Taveira | 2021-10-18 20:15:59 | Re: ALTER TABLE ... SET DATA TYPE removes statistics |
| Previous Message | PG Doc comments form | 2021-10-18 10:17:14 | pmap grep zero fail to load vm_peak |