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

Commit 0e3afb3

Browse files
committed
Minor improvements in descriptions of recent changes.
1 parent 67c1fd1 commit 0e3afb3

File tree

1 file changed

+14
-9
lines changed

1 file changed

+14
-9
lines changed

doc/src/sgml/release.sgml

Lines changed: 14 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
<!--
2-
$PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.319 2005/01/15 05:59:44 momjian Exp $
2+
$PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.320 2005/01/15 07:53:04 tgl Exp $
33
-->
44

55
<appendix id="release">
@@ -648,14 +648,18 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.319 2005/01/15 05:59:44 momjian
648648

649649
<listitem>
650650
<para>
651-
Improve optimizer row estimates for non-<command>VACUUM</command>ed
652-
tables (Tom)
651+
Improve optimizer rowcount estimates (Tom)
653652
</para>
654653
<para>
655-
The system now uses the number of blocks in the table to estimate the
656-
number of rows in the table if it has never been
657-
<command>VACUUM</command>ed or <command>ANALYZE</command>d.
658-
Previously a fixed value was used in such cases.
654+
Formerly the planner estimated table sizes using the values seen
655+
by the last <command>VACUUM</command> or <command>ANALYZE</command>,
656+
both as to physical table size (number of pages) and number of rows.
657+
Now, the physical table size is obtained directly from the kernel,
658+
and the number of rows is estimated by multiplying the table size
659+
by the row density (rows per page) seen by the last
660+
<command>VACUUM</command> or <command>ANALYZE</command>. This should
661+
produce more reliable estimates in cases where the table size has
662+
changed significantly since the last housekeeping command.
659663
</para>
660664
</listitem>
661665

@@ -1744,10 +1748,11 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.319 2005/01/15 05:59:44 momjian
17441748

17451749
<listitem>
17461750
<para>
1747-
Allow PL/pgSQL to understand <command>ELSEIF</> (Neil)
1751+
Accept <command>ELSEIF</> in PL/pgSQL (Neil)
17481752
</para>
17491753
<para>
1750-
Previously PL/pgSQL only understood <command>ELSIF</>.
1754+
Previously PL/pgSQL only allowed <command>ELSIF</>, but many people
1755+
are accustomed to spelling this keyword <command>ELSEIF</>.
17511756
</para>
17521757
</listitem>
17531758

0 commit comments

Comments
 (0)