mirror of
https://github.com/postgres/postgres.git
synced 2025-04-27 22:56:53 +03:00
Release note updates.
This commit is contained in:
parent
53a04e005b
commit
e889ff4def
@ -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">
|
||||
@ -30,21 +30,22 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.343 2005/08/23 12:46:35 momjian
|
||||
<listitem>
|
||||
<para>
|
||||
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>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term>
|
||||
Allow indexes to be used for MIN/MAX (Tom)
|
||||
Automatically use indexes for MIN() and MAX() (Tom)
|
||||
</term>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
In previous releases, the only way to use index for MIN/MAX was to rewrite
|
||||
the query as SELECT col FROM tab ORDER BY col LIMIT 1. This now happens
|
||||
automatically.
|
||||
In previous releases, the only way to use an index for MIN/MAX
|
||||
was to rewrite the query as SELECT col FROM tab ORDER BY col
|
||||
LIMIT 1. Index usage now happens automatically.
|
||||
</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
Loading…
x
Reference in New Issue
Block a user