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-22 21:03:29
Message-ID: aAgEIXZ9zlqThJCZ@msg.df7cb.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

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.

Christoph

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Nathan Bossart 2025-04-22 21:29:21 Re: pgsql: Update guidance for running vacuumdb after pg_upgrade.
Previous Message Nathan Bossart 2025-04-22 20:54:30 Re: pgsql: Update guidance for running vacuumdb after pg_upgrade.

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Geoghegan 2025-04-22 21:16:49 Re: index prefetching
Previous Message Nathan Bossart 2025-04-22 20:54:30 Re: pgsql: Update guidance for running vacuumdb after pg_upgrade.