Re: pgsql: Update guidance for running vacuumdb after pg_upgrade.

From: Christoph Berg <myon(at)debian(dot)org>
To: Nathan Bossart <nathandbossart(at)gmail(dot)com>
Cc: Corey Huinker <corey(dot)huinker(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: pgsql: Update guidance for running vacuumdb after pg_upgrade.
Date: 2025-04-23 14:10:56
Message-ID: aAj08PiW0CX7OWY9@msg.df7cb.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

Re: Nathan Bossart
> pg_log(PG_REPORT,
> + "Some statistics are not transferred by pg_upgrade.\n"
> "Once you start the new server, consider running:\n"
> + " %s/vacuumdb %s--all --analyze-in-stages --missing-stats-only\n"
> + " %s/vacuumdb %s--all --analyze-only",

I would make it "Once you start the new server, run these two commands:"
to make it explicit that both should be run, not alternatively either.

This patch addresses my concern, thanks.

Christoph

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Nathan Bossart 2025-04-23 14:33:17 Re: vacuumdb --missing-stats-only and pg_upgrade from PG13
Previous Message Christoph Berg 2025-04-23 14:01:33 vacuumdb --missing-stats-only and pg_upgrade from PG13

Browse pgsql-hackers by date

  From Date Subject
Next Message Nathan Bossart 2025-04-23 14:33:17 Re: vacuumdb --missing-stats-only and pg_upgrade from PG13
Previous Message Christoph Berg 2025-04-23 14:01:33 vacuumdb --missing-stats-only and pg_upgrade from PG13