|
1 | 1 | <!-- |
2 | | -$PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.319 2005/01/1505:59:44 momjian Exp $ |
| 2 | +$PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.320 2005/01/1507:53:04 tgl Exp $ |
3 | 3 | --> |
4 | 4 |
|
5 | 5 | <appendix id="release"> |
@@ -648,14 +648,18 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.319 2005/01/15 05:59:44 momjian |
648 | 648 |
|
649 | 649 | <listitem> |
650 | 650 | <para> |
651 | | - Improve optimizer row estimates for non-<command>VACUUM</command>ed |
652 | | - tables (Tom) |
| 651 | + Improve optimizer rowcount estimates (Tom) |
653 | 652 | </para> |
654 | 653 | <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. |
659 | 663 | </para> |
660 | 664 | </listitem> |
661 | 665 |
|
@@ -1744,10 +1748,11 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.319 2005/01/15 05:59:44 momjian |
1744 | 1748 |
|
1745 | 1749 | <listitem> |
1746 | 1750 | <para> |
1747 | | -Allow PL/pgSQL to understand<command>ELSEIF</> (Neil) |
| 1751 | +Accept<command>ELSEIF</> in PL/pgSQL (Neil) |
1748 | 1752 | </para> |
1749 | 1753 | <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</>. |
1751 | 1756 | </para> |
1752 | 1757 | </listitem> |
1753 | 1758 |
|
|