Further adjust guidance for running vacuumdb after pg_upgrade.
Nathan Bossart <nathan@postgresql.org>
Further adjust guidance for running vacuumdb after pg_upgrade. Since pg_upgrade does not transfer the cumulative statistics used to trigger autovacuum and autoanalyze, the server may take much longer than expected to process them post-upgrade. Currently, we recommend analyzing only relations for which optimizer statistics were not transferred by using the --analyze-in-stages and --missing-stats-only options. This commit appends another recommendation to analyze all relations to update the relevant cumulative statistics by using the --analyze-only option. This is similar to the recommendation for pg_stat_reset(). Reported-by: Christoph Berg <myon@debian.org> Reviewed-by: Christoph Berg <myon@debian.org> Discussion: https://postgr.es/m/aAfxfKC82B9NvJDj%40msg.df7cb.de
Files
| Path | Change | +/− |
|---|---|---|
| doc/src/sgml/ref/pgupgrade.sgml | modified | +7 −5 |
| src/bin/pg_upgrade/check.c | modified | +6 −3 |
Documentation touched
Discussion
- pgsql: Update guidance for running vacuumdb after pg_upgrade. 12 messages · 2025-03-18 → 2025-04-30