mirror of
https://github.com/postgres/postgres.git
synced 2025-06-03 00:02:26 -04:00
Adjust SGML so major feature items are all not in a single subparagraph.
This commit is contained in:
parent
2a49282477
commit
3a3c06f0e0
@ -1,5 +1,5 @@
|
||||
<!--
|
||||
$PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.339 2005/08/23 11:32:33 momjian Exp $
|
||||
$PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.340 2005/08/23 11:53:33 momjian Exp $
|
||||
-->
|
||||
|
||||
<appendix id="release">
|
||||
@ -18,8 +18,37 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.339 2005/08/23 11:32:33 momjian
|
||||
|
||||
<para>
|
||||
Major changes in this release:
|
||||
</para>
|
||||
|
||||
<variablelist>
|
||||
|
||||
<varlistentry>
|
||||
<term>
|
||||
Improve concurrent access to the shared buffer cache (Tom)
|
||||
</term>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
This was accomplished by eliminating global locks and using a clock
|
||||
sweep algorithm to find free buffers.
|
||||
</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term>
|
||||
Allow indexes to be used for MIN/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.
|
||||
</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term>
|
||||
</term>
|
||||
@ -27,12 +56,40 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.339 2005/08/23 11:32:33 momjian
|
||||
<listitem>
|
||||
<para>
|
||||
</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term>
|
||||
</term>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term>
|
||||
</term>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term>
|
||||
</term>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
</variablelist>
|
||||
</para>
|
||||
</sect2>
|
||||
|
||||
<sect2>
|
||||
@ -140,16 +197,7 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.339 2005/08/23 11:32:33 momjian
|
||||
<listitem>
|
||||
<para>
|
||||
Improve rtree index capabilities and performance (Neil)
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
Improve concurrent access to the shared buffer cache (Tom)
|
||||
</para>
|
||||
<para>
|
||||
This was accomplished by eliminating global locks and using a clock
|
||||
sweep algorithm to find free buffers.
|
||||
Replaced by contrib?
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
@ -165,17 +213,6 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.339 2005/08/23 11:32:33 momjian
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
Allow indexes to be used for MIN/MAX (Tom)
|
||||
</para>
|
||||
<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.
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
Add in-memory bitmaps which allows multiple indexes to be merged in a
|
||||
@ -1839,6 +1876,7 @@ typedefs (Michael)</para></listitem>
|
||||
|
||||
<para>
|
||||
Major changes in this release:
|
||||
</para>
|
||||
|
||||
<variablelist>
|
||||
<varlistentry>
|
||||
@ -1988,7 +2026,6 @@ typedefs (Michael)</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
</variablelist>
|
||||
</para>
|
||||
</sect2>
|
||||
|
||||
<sect2>
|
||||
@ -4889,6 +4926,7 @@ DROP SCHEMA information_schema CASCADE;
|
||||
|
||||
<para>
|
||||
Major changes in this release:
|
||||
</para>
|
||||
|
||||
<variablelist>
|
||||
<varlistentry>
|
||||
@ -5152,8 +5190,8 @@ DROP SCHEMA information_schema CASCADE;
|
||||
</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
</variablelist>
|
||||
</para>
|
||||
</sect2>
|
||||
|
||||
<sect2>
|
||||
@ -7396,6 +7434,7 @@ operations on bytea columns (Joe)</para></listitem>
|
||||
|
||||
<para>
|
||||
Major changes in this release:
|
||||
</para>
|
||||
|
||||
<variablelist>
|
||||
<varlistentry>
|
||||
@ -7512,7 +7551,6 @@ operations on bytea columns (Joe)</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
</variablelist>
|
||||
</para>
|
||||
</sect2>
|
||||
|
||||
<sect2>
|
||||
@ -8396,6 +8434,7 @@ since <productname>PostgreSQL</productname> 7.1.
|
||||
|
||||
<para>
|
||||
Major changes in this release:
|
||||
</para>
|
||||
|
||||
<variablelist>
|
||||
<varlistentry>
|
||||
@ -8470,8 +8509,8 @@ since <productname>PostgreSQL</productname> 7.1.
|
||||
</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
</variablelist>
|
||||
</para>
|
||||
</sect2>
|
||||
|
||||
<sect2>
|
||||
@ -9070,6 +9109,7 @@ Python fixes (Darcy)
|
||||
|
||||
<para>
|
||||
Major changes in this release:
|
||||
</para>
|
||||
|
||||
<variablelist>
|
||||
<varlistentry>
|
||||
@ -9533,6 +9573,7 @@ ecpg changes (Michael)
|
||||
|
||||
<para>
|
||||
Major changes in this release:
|
||||
</para>
|
||||
|
||||
<variablelist>
|
||||
<varlistentry>
|
||||
@ -9586,9 +9627,9 @@ ecpg changes (Michael)
|
||||
column correlation names.
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
</para>
|
||||
|
||||
<sect2>
|
||||
<title>Migration to version 7.0</title>
|
||||
@ -9606,6 +9647,7 @@ ecpg changes (Michael)
|
||||
<para>
|
||||
Interface and compatibility issues to consider for the new
|
||||
release include:
|
||||
</para>
|
||||
|
||||
<itemizedlist>
|
||||
<listitem>
|
||||
@ -9652,8 +9694,6 @@ ecpg changes (Michael)
|
||||
</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
</para>
|
||||
|
||||
</sect2>
|
||||
|
||||
<sect2>
|
||||
|
Loading…
x
Reference in New Issue
Block a user