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

From Frédéric Yhuel
Subject Re: vacuumdb changes for stats import/export
Date
Msg-id b527f417-b27c-43bb-8623-4c703fc0ad72@dalibo.com
Whole thread Raw
In response to Re: vacuumdb changes for stats import/export  (Nathan Bossart <nathandbossart@gmail.com>)
Responses Re: vacuumdb changes for stats import/export
List pgsql-hackers

On 7/28/25 16:47, Nathan Bossart wrote:
> 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.

Aha, it makes sense now, thank you!

> 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..."

I vote for the second option.




pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Making pgfdw_report_error statically analyzable
Next
From: Jean-Christophe Arnu
Date:
Subject: Re: restore_command return code behaviour