database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-07-30 11:03:19 +03:00
Code Activity

Update guidance for running vacuumdb after pg_upgrade.

Browse Source 
Now that pg_upgrade can carry over most optimizer statistics, we
should recommend using vacuumdb's new --missing-stats-only option
to only analyze relations that are missing statistics.

Reviewed-by: John Naylor <johncnaylorls@gmail.com>
Discussion: https://postgr.es/m/Z5O1bpcwDrMgyrYy%40nathan
This commit is contained in:
Nathan Bossart
2025-03-18 16:32:56 -05:00
parent edba754f05
commit c9d502eb68
2 changed files with 6 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
doc/src/sgml/ref/pgupgrade.sgml
View File

@ -807,10 +807,11 @@ psql --username=postgres --file=script.sql postgres
</para>
<para>
Using <command>vacuumdb --all --analyze-only</command> can efficiently
generate such statistics, and the use of <option>--jobs</option>
can speed it up. Option <option>--analyze-in-stages</option>
can be used to generate minimal statistics quickly.
Using <command>vacuumdb --all --analyze-only --missing-stats-only</command>
can efficiently generate such statistics. Alternatively,
<command>vacuumdb --all --analyze-in-stages --missing-stats-only</command>
can be used to generate minimal statistics quickly. For either command,
the use of <option>--jobs</option> can speed it up.
If <varname>vacuum_cost_delay</varname> is set to a non-zero
value, this can be overridden to speed up statistics generation
using <envar>PGOPTIONS</envar>, e.g., <literal>PGOPTIONS='-c