rdelaage
/
postgresql
mirror of https://git.postgresql.org/git/postgresql.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Copy-edit vacuuumdb --analyze-in-stages doc blurb 

I had made a few typos, and Nikolai Berkoff made a wording change
suggestion.

Discussion: https://postgr.es/m/VMwe7-sGegrQPQ7fJjSCdsEbESKeJFOb6G4DFxxNrf45I7DzHio7sNUH88wWRMnAy5a5G0-FB31dxPM47ldigW6WdiCPncHgqO9bNl6F240=@pm.me
This commit is contained in:
Alvaro Herrera 2021-11-26 14:42:15 -03:00
parent 013bb6c8c0
commit dd484c97f5
No known key found for this signature in database
GPG Key ID: 1C20ACB9D5C564AE
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
doc/src/sgml/ref/vacuumdb.sgml
View File

@ -397,7 +397,7 @@ PostgreSQL documentation
<listitem>
<para>
Only calculate statistics for use by the optimizer (no vacuum),
like <option>--analyze-only</option>. Run several (currently three)
like <option>--analyze-only</option>. Run three
stages of analyze; the first stage uses the lowest possible statistics
target (see <xref linkend="guc-default-statistics-target"/>)
to produce usable statistics faster, and subsequent stages build the
@ -405,10 +405,10 @@ PostgreSQL documentation
</para>
<para>
This option is only useful to analyze a database that current has
no statistics or wholly incorrect ones, such as if it is newly
This option is only useful to analyze a database that currently has
no statistics or has wholly incorrect ones, such as if it is newly
populated from a restored dump or by <command>pg_upgrade</command>.
Be aware that running this option in a database with existing
Be aware that running with this option in a database with existing
statistics may cause the query optimizer choices to become
transiently worse due to the low statistics targets of the early
stages.