Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mcX8C-00039e-6S for pgsql-docs@arkaria.postgresql.org; Mon, 18 Oct 2021 18:13:04 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1mcX8B-0004bi-13 for pgsql-docs@arkaria.postgresql.org; Mon, 18 Oct 2021 18:13:03 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mcX89-0004Zi-H0 for pgsql-docs@lists.postgresql.org; Mon, 18 Oct 2021 18:13:02 +0000 Received: from out5-smtp.messagingengine.com ([66.111.4.29]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mcX85-0001L3-TH for pgsql-docs@lists.postgresql.org; Mon, 18 Oct 2021 18:13:01 +0000 Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 1E48F5C010B; Mon, 18 Oct 2021 14:12:56 -0400 (EDT) Received: from imap21 ([10.202.2.71]) by compute1.internal (MEProxy); Mon, 18 Oct 2021 14:12:56 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eulerto.com; h= mime-version:message-id:in-reply-to:references:date:from:to :subject:content-type; s=fm3; bh=1L5zwkir8N1ZZM6MhP5JfzRS7PIheSI 0npdetp3Af9c=; b=S0JywRzfcAxegVGCKXkvdMw9Bc2hpFU+mhiYkDVyFFUJ3cD PvQszmL9F/26H8HM68uFHcdeOP1qlkkFg+ELiKjPOxsMv7qACeZkZszPt7OsabGr s91gJ62Uaq8VsR/UK36sdtRKg94H8z5/Tt/FjNTD0AJ0hpIR9SE9DRao+3sSulVb hqd+HRQTDQbP9vRf+jI3WK2pgVUwkIZZQ9uOowgn1uKmudBS+kHgwMcTts+HPERt Y/1MyjhdytBNRXAtyKkFtAuGQnOjcLgZZYlf3o9yJUgQQWUPhkRQMKSnd0JoxDn9 0udF/djpgEc9IyRPfJ/0HyGQBn2dnDXYNsdjATA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=1L5zwk ir8N1ZZM6MhP5JfzRS7PIheSI0npdetp3Af9c=; b=XFBM3CABq/J60UqCorYxBn IwFL/ZWmtw2qPoy/acbzBM6X2wYcIPBV3/pUlJv5IkIF7vacAEn0/GuT4PObzi8q A44q98tEoH7f37OWwhvz8G3HMxX0KGupHxqcSrfItOqjt7cnT6vBKUGj7MWBkGCX F1s/uYpNfJUQsu4pCrD9s5zUM/w8pt2LfJxbuqmy7gwTdQ8ouV0glQVu+ygOvFgy 8V8e77t8YqkfEXX60HeBDtFitGbSnG3RsCD3TzKl/Q6bddSAqi/yiEwoUg46LF1N dmn6h0uekABiaX5SZ3jPk+aFIpTSuoofvFgi4yFfrOUi1yRdpPXLfA7hJY3LgqOg == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvtddrvddvtddguddukecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecunecujfgurhepofgfggfkjghffffhvffutgesrg dtreerreertdenucfhrhhomhepfdfguhhlvghrucfvrghvvghirhgrfdcuoegvuhhlvghr segvuhhlvghrthhordgtohhmqeenucggtffrrghtthgvrhhnpeejtefhuedvgffftdetve dufedtjeeuffekleevkefhveekgeelfefhjeehtdejgeenucffohhmrghinhepvghnthgv rhhprhhishgvuggsrdgtohhmnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpe hmrghilhhfrhhomhepvghulhgvrhesvghulhgvrhhtohdrtghomh X-ME-Proxy: Received: by mailuser.nyi.internal (Postfix, from userid 501) id 590D251C0060; Mon, 18 Oct 2021 14:12:55 -0400 (EDT) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.5.0-alpha0-1345-g8441cd7852-fm-20211006.001-g8441cd78 Mime-Version: 1.0 Message-Id: In-Reply-To: References: Date: Mon, 18 Oct 2021 15:12:34 -0300 From: "Euler Taveira" To: "nikolai.berkoff" , "pgsql-docs@lists.postgresql.org" Subject: Re: vacuumdb --analyze-in-stages Content-Type: multipart/alternative; boundary=7097321f2e534a408b78f9e8a31df304 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --7097321f2e534a408b78f9e8a31df304 Content-Type: text/plain 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/ --7097321f2e534a408b78f9e8a31df304 Content-Type: text/html Content-Transfer-Encoding: quoted-printable
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 befo= re they are improved.  This could be made clearer in the documentat= ion.
I think the paragraph you modified *alre= ady* 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_ (prod= uce usable statistics faster).


--
Euler Taveira
EDB &nb= sp; https://www.enterprisedb.c= om/

--7097321f2e534a408b78f9e8a31df304--