1
1
<!--
2
- $PostgreSQL: pgsql/doc/src/sgml/ref/analyze.sgml,v 1.24 2008/11/14 10:22:45 petere Exp $
2
+ $PostgreSQL: pgsql/doc/src/sgml/ref/analyze.sgml,v 1.25 2008/12/13 19:13:44 tgl Exp $
3
3
PostgreSQL documentation
4
4
-->
5
5
@@ -132,10 +132,10 @@ ANALYZE [ VERBOSE ] [ <replaceable class="PARAMETER">table</replaceable> [ ( <re
132
132
will change slightly each time <command>ANALYZE</command> is run,
133
133
even if the actual table contents did not change. This might result
134
134
in small changes in the planner's estimated costs shown by
135
- <xref linkend="sql-explain" endterm="sql-explain-title">. In rare situations, this
136
- non-determinism will cause thequery optimizer to choose a
137
- different queryplan between runs of <command>ANALYZE</command>. To
138
- avoid this, raise the amount of statistics collected by
135
+ <xref linkend="sql-explain" endterm="sql-explain-title">.
136
+ In rare situations, this non-determinism will cause theplanner's
137
+ choices of queryplans to change after <command>ANALYZE</command> is run.
138
+ To avoid this, raise the amount of statistics collected by
139
139
<command>ANALYZE</command>, as described below.
140
140
</para>
141
141
@@ -148,7 +148,7 @@ ANALYZE [ VERBOSE ] [ <replaceable class="PARAMETER">table</replaceable> [ ( <re
148
148
endterm="sql-altertable-title">). The target value sets the
149
149
maximum number of entries in the most-common-value list and the
150
150
maximum number of bins in the histogram. The default target value
151
- is10 , but this can be adjusted up or down to trade off accuracy of
151
+ is100 , but this can be adjusted up or down to trade off accuracy of
152
152
planner estimates against the time taken for
153
153
<command>ANALYZE</command> and the amount of space occupied in
154
154
<literal>pg_statistic</literal>. In particular, setting the