database/postgres
database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-04-27 22:56:53 +03:00
Code

Release note updates.

Browse Source
This commit is contained in:
Bruce Momjian 2005-08-23 12:47:30 +00:00
parent 53a04e005b
commit e889ff4def
1 changed files with 7 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
doc/src/sgml/release.sgml
View File

@ -1,5 +1,5 @@
<!-- <!--
$PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.343 2005/08/23 12:46:35 momjian Exp $ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.344 2005/08/23 12:47:30 momjian Exp $
--> -->
<appendix id="release"> <appendix id="release">
@ -30,21 +30,22 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.343 2005/08/23 12:46:35 momjian
<listitem> <listitem>
<para> <para>
This was accomplished by eliminating global locks and using a clock This was accomplished by eliminating global locks and using a clock
sweep algorithm to find free buffers. sweep algorithm to find free buffers. This increases scalability
on multi-CPU systems.
</para> </para>
</listitem> </listitem>
</varlistentry> </varlistentry>
<varlistentry> <varlistentry>
<term> <term>
Allow indexes to be used for MIN/MAX (Tom) Automatically use indexes for MIN() and MAX() (Tom)
</term> </term>
<listitem> <listitem>
<para> <para>
In previous releases, the only way to use index for MIN/MAX was to rewrite In previous releases, the only way to use an index for MIN/MAX
the query as SELECT col FROM tab ORDER BY col LIMIT 1. This now happens was to rewrite the query as SELECT col FROM tab ORDER BY col
automatically. LIMIT 1. Index usage now happens automatically.
</para> </para>
</listitem> </listitem>
</varlistentry> </varlistentry>