Re: pgsql: Update guidance for running vacuumdb after pg_upgrade. - Mailing list pgsql-hackers

From Nathan Bossart
Subject Re: pgsql: Update guidance for running vacuumdb after pg_upgrade.
Date
Msg-id aAgKMavWTlgjWkar@nathan
Whole thread Raw
In response to Re: pgsql: Update guidance for running vacuumdb after pg_upgrade.  (Christoph Berg <myon@debian.org>)
Responses Re: pgsql: Update guidance for running vacuumdb after pg_upgrade.
List pgsql-hackers
On Tue, Apr 22, 2025 at 11:03:29PM +0200, Christoph Berg wrote:
> Re: Nathan Bossart
>> In any case, IMO it's unfortunate
>> that we might end up recommending roughly the same post-upgrade steps as
>> before even though the optimizer statistics are carried over.
> 
> Maybe the docs (and the pg_upgrade scripts) should recommend the old
> procedure by default until this gap is closed? People could then still
> opt to use the new procedure in specific cases.

I think we'd still want to modify the --analyze-in-stages recommendation
(from what is currently recommended for supported versions).  If we don't,
you'll wipe out the optimizer stats you brought over from the old version.

Here is a rough draft of what I am thinking.

-- 
nathan

Attachment

pgsql-hackers by date:

Previous
From: Ivan Kush
Date:
Subject: Re: [PoC] Federated Authn/z with OAUTHBEARER
Next
From: Christoph Berg
Date:
Subject: Re: What's our minimum supported Python version?