From: Euler Taveira <euler@eulerto.com>
To: nikolai.berkoff <nikolai.berkoff@pm.me>
To: pgsql-docs@lists.postgresql.org <pgsql-docs@lists.postgresql.org>
Subject: Re: vacuumdb --analyze-in-stages
Date: Mon, 18 Oct 2021 15:12:34 -0300
Message-ID: <c34d7d46-ef28-4fd2-84bb-7d38b039aae9@www.fastmail.com> (raw)
In-Reply-To: <s-kSljtWXMWgMfGTztPTPcS80R8FHdOrBxDTnrQI6GMZbT7au1A4b0fzaSFtKwCI8nwN0MhgPLfVOTvJ7DwTjkip4P3d0o4VgrMJs4OLN-o=@pm.me>
References: <s-kSljtWXMWgMfGTztPTPcS80R8FHdOrBxDTnrQI6GMZbT7au1A4b0fzaSFtKwCI8nwN0MhgPLfVOTvJ7DwTjkip4P3d0o4VgrMJs4OLN-o=@pm.me>
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/
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-docs@postgresql.org
Cc: euler@eulerto.com, nikolai.berkoff@pm.me, pgsql-docs@lists.postgresql.org
Subject: Re: vacuumdb --analyze-in-stages
In-Reply-To: <c34d7d46-ef28-4fd2-84bb-7d38b039aae9@www.fastmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox