Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commit00a354a

Browse files
committed
Reword doc blurb for vacuumdb --analyze-in-stages
Make users aware that using it in a database with existing stats mightcause transient problems.Author: Nikolai Berkoff <nikolai.berkoff@pm.me>Discussion:https://postgr.es/m/s-kSljtWXMWgMfGTztPTPcS80R8FHdOrBxDTnrQI6GMZbT7au1A4b0fzaSFtKwCI8nwN0MhgPLfVOTvJ7DwTjkip4P3d0o4VgrMJs4OLN-o=@pm.me
1 parentbef47ff commit00a354a

File tree

1 file changed

+10
-6
lines changed

1 file changed

+10
-6
lines changed

‎doc/src/sgml/ref/vacuumdb.sgml

Lines changed: 10 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -398,15 +398,19 @@ PostgreSQL documentation
398398
<para>
399399
Only calculate statistics for use by the optimizer (no vacuum),
400400
like <option>--analyze-only</option>. Run several (currently three)
401-
stages of analyze with different configuration settings, to produce
402-
usable statistics faster.
401+
stages of analyze; the first stage uses the lowest possible statistics
402+
target (see <xref linkend="guc-default-statistics-target"/>)
403+
to produce usable statistics faster, and subsequent stages build the
404+
full statistics.
403405
</para>
404406

405407
<para>
406-
This option is useful to analyze a database that was newly populated
407-
from a restored dump or by <command>pg_upgrade</command>. This option
408-
will try to create some statistics as fast as possible, to make the
409-
database usable, and then produce full statistics in the subsequent
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
410+
populated from a restored dump or by <command>pg_upgrade</command>.
411+
Be aware that running this option in a database with existing
412+
statistics may cause the query optimizer choices to become
413+
transiently worse due to the low statistics targets of the early
410414
stages.
411415
</para>
412416
</listitem>

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp