Re: vacuumdb changes for stats import/export - Mailing list pgsql-hackers

From Nathan Bossart
Subject Re: vacuumdb changes for stats import/export
Date
Msg-id aIeNeo-zGgevViNc@nathan
Whole thread Raw
In response to Re: vacuumdb changes for stats import/export  (Frédéric Yhuel <frederic.yhuel@dalibo.com>)
Responses Re: vacuumdb changes for stats import/export
List pgsql-hackers
On Sun, Jul 27, 2025 at 12:46:44PM +0200, Frédéric Yhuel wrote:
> Then it seems very unlikely that the query optimizer's choices become
> transiently worse because of that, doesn't it? and this shouldn't be used to
> justify this option, IMHO.

I can't remember who wrote this line, but it was borrowed from the
--analyze-in-stages description.  The point is that if you use
--analyze-in-stages without --missing-stats-only, there will be a period
where existing statistics will be replaced with ones generated with lower
statistics targets.  Obviously, this wording isn't clear enough.  We might
need to either remove that sentence or add "When used in conjunction with
--analyze-in-stages..."

-- 
nathan



pgsql-hackers by date:

Previous
From: Tomas Vondra
Date:
Subject: Re: Adding basic NUMA awareness
Next
From: Tom Lane
Date:
Subject: Making pgfdw_report_error statically analyzable