Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content

Commit dd484c9

Browse files
committed
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
1 parent 013bb6c commit dd484c9

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

doc/src/sgml/ref/vacuumdb.sgml

+4-4
Original file line numberDiff line numberDiff line change
@@ -397,18 +397,18 @@ PostgreSQL documentation
397397
<listitem>
398398
<para>
399399
Only calculate statistics for use by the optimizer (no vacuum),
400-
like <option>--analyze-only</option>. Run several (currently three)
400+
like <option>--analyze-only</option>. Run three
401401
stages of analyze; the first stage uses the lowest possible statistics
402402
target (see <xref linkend="guc-default-statistics-target"/>)
403403
to produce usable statistics faster, and subsequent stages build the
404404
full statistics.
405405
</para>
406406

407407
<para>
408-
This option is only useful to analyze a database that current has
409-
no statistics or wholly incorrect ones, such as if it is newly
408+
This option is only useful to analyze a database that currently has
409+
no statistics or has wholly incorrect ones, such as if it is newly
410410
populated from a restored dump or by <command>pg_upgrade</command>.
411-
Be aware that running this option in a database with existing
411+
Be aware that running with this option in a database with existing
412412
statistics may cause the query optimizer choices to become
413413
transiently worse due to the low statistics targets of the early
414414
stages.

0 commit comments

Comments
 (0)