|
1 | 1 | <!-- |
2 | | -$PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.343 2005/08/23 12:46:35 momjian Exp $ |
| 2 | +$PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.344 2005/08/23 12:47:30 momjian Exp $ |
3 | 3 | --> |
4 | 4 |
|
5 | 5 | <appendix id="release"> |
@@ -30,21 +30,22 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.343 2005/08/23 12:46:35 momjian |
30 | 30 | <listitem> |
31 | 31 | <para> |
32 | 32 | This was accomplished by eliminating global locks and using a clock |
33 | | - sweep algorithm to find free buffers. |
| 33 | + sweep algorithm to find free buffers. This increases scalability |
| 34 | + on multi-CPU systems. |
34 | 35 | </para> |
35 | 36 | </listitem> |
36 | 37 | </varlistentry> |
37 | 38 |
|
38 | 39 | <varlistentry> |
39 | 40 | <term> |
40 | | -Allowindexesto be usedfor MIN/MAX (Tom) |
| 41 | +Automatically useindexes for MIN() andMAX() (Tom) |
41 | 42 | </term> |
42 | 43 |
|
43 | 44 | <listitem> |
44 | 45 | <para> |
45 | | - In previous releases, the only way to use index for MIN/MAX was to rewrite |
46 | | - the query as SELECT col FROM tab ORDER BY col LIMIT 1. This now happens |
47 | | - automatically. |
| 46 | + In previous releases, the only way to useanindex for MIN/MAX |
| 47 | +was to rewritethe query as SELECT col FROM tab ORDER BY col |
| 48 | +LIMIT 1. Index usage now happensautomatically. |
48 | 49 | </para> |
49 | 50 | </listitem> |
50 | 51 | </varlistentry> |
|