database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-07-03 20:02:46 +03:00
Code Activity

Further adjust guidance for running vacuumdb after pg_upgrade.

Browse Source 
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
This commit is contained in:
Nathan Bossart
2025-04-30 14:12:59 -05:00
parent f60420cff6
commit d5f1b6a75b
2 changed files with 13 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
src/bin/pg_upgrade/check.c
View File

@ -814,9 +814,12 @@ output_completion_banner(char *deletion_script_file_name)
}
pg_log(PG_REPORT,
"Some optimizer statistics may not have been transferred by pg_upgrade.\n"
"Once you start the new server, consider running:\n"
" %s/vacuumdb %s--all --analyze-in-stages --missing-stats-only", new_cluster.bindir, user_specification.data);
"Some statistics are not transferred by pg_upgrade.\n"
"Once you start the new server, consider running these two commands:\n"
" %s/vacuumdb %s--all --analyze-in-stages --missing-stats-only\n"
" %s/vacuumdb %s--all --analyze-only",
new_cluster.bindir, user_specification.data,
new_cluster.bindir, user_specification.data);
if (deletion_script_file_name)
pg_log(PG_REPORT,