Commit 04c779d3 authored by Tom Lane's avatar Tom Lane

Fix markup so that 'make HISTORY' works. A couple very minor

editorial improvements.
parent 0f1ac2d0
<!-- $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.596 2009/03/26 02:48:53 momjian Exp $ --> <!-- $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.597 2009/03/26 03:46:14 tgl Exp $ -->
<!-- <!--
Typical markup: Typical markup:
...@@ -68,7 +68,7 @@ do it for earlier branch release files. ...@@ -68,7 +68,7 @@ do it for earlier branch release files.
<note> <note>
<title>Release date</title> <title>Release date</title>
<simpara>2009-XX-XX, ITEMS CURRENT AS OF 2009-03-16</simpara> <simpara>2009-XX-XX, ITEMS CURRENT AS OF 2009-03-16</simpara>
</note> </note>
<sect2> <sect2>
...@@ -155,13 +155,13 @@ do it for earlier branch release files. ...@@ -155,13 +155,13 @@ do it for earlier branch release files.
<listitem> <listitem>
<para> <para>
Disable appending of the epoch date/time when '%' escapes are missing in Disable appending of the epoch date/time when no '%' escapes are
log_filename (Robert Haas) present in log_filename (Robert Haas)
</para> </para>
<para> <para>
This change was made because some users wanted a consistent log This change was made because some users wanted a constant log filename,
filename. for use with an external log rotation tool.
</para> </para>
</listitem> </listitem>
...@@ -304,8 +304,8 @@ do it for earlier branch release files. ...@@ -304,8 +304,8 @@ do it for earlier branch release files.
<listitem> <listitem>
<para> <para>
Throw an error of an escape character is the last character in a LIKE Throw an error if an escape character is the last character in a LIKE
pattern (nothing to escape) (Tom) pattern (it has nothing to escape) (Tom)
</para> </para>
</listitem> </listitem>
...@@ -350,8 +350,8 @@ do it for earlier branch release files. ...@@ -350,8 +350,8 @@ do it for earlier branch release files.
<listitem> <listitem>
<para> <para>
Remove ~=~ and ~<>~ operators used for LIKE index comparisons (Tom) bjm: Remove ~=~ and ~&lt;&gt;~ operators used for LIKE index comparisons
needed? (Tom) bjm: needed?
</para> </para>
<para> <para>
...@@ -543,7 +543,7 @@ do it for earlier branch release files. ...@@ -543,7 +543,7 @@ do it for earlier branch release files.
<listitem> <listitem>
<para> <para>
Add postgresql.conf setting cursor_tuple_fraction to control the Add postgresql.conf setting cursor_tuple_fraction to control the
fraction of a cursor's rows expected to be requested by the user (Robert fraction of a cursor's rows expected to be requested by the user (Robert
Hell) Hell)
</para> </para>
...@@ -937,7 +937,7 @@ do it for earlier branch release files. ...@@ -937,7 +937,7 @@ do it for earlier branch release files.
<listitem> <listitem>
<para> <para>
OFFSET num {ROW|ROWS} FETCH {FIRST|NEXT} [num] {ROW|ROWS} ONLY. OFFSET num {ROW|ROWS} FETCH {FIRST|NEXT} [num] {ROW|ROWS} ONLY.
</para> </para>
</listitem> </listitem>
...@@ -971,7 +971,7 @@ do it for earlier branch release files. ...@@ -971,7 +971,7 @@ do it for earlier branch release files.
<listitem> <listitem>
<para> <para>
New syntax supported (these formerly required "ALTER TABLE") New syntax supported (these formerly required "ALTER TABLE")
</para> </para>
</listitem> </listitem>
...@@ -985,17 +985,17 @@ do it for earlier branch release files. ...@@ -985,17 +985,17 @@ do it for earlier branch release files.
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
ALTER VIEW ALTER COLUMN SET/DROP DEFAULT ALTER VIEW ALTER COLUMN SET/DROP DEFAULT
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
ALTER VIEW OWNER TO ALTER VIEW OWNER TO
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
ALTER VIEW SET SCHEMA ALTER VIEW SET SCHEMA
</para> </para>
</listitem> </listitem>
</itemizedlist> </itemizedlist>
...@@ -1181,14 +1181,13 @@ do it for earlier branch release files. ...@@ -1181,14 +1181,13 @@ do it for earlier branch release files.
<para> <para>
Previously EXPLAIN VERBOSE output an internal representation of the Previously EXPLAIN VERBOSE output an internal representation of the
output columns. query plan. (That behavior is now available via debug_print_plan.)
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
Have EXPLAIN honor debug_print_plan (Tom) bjm: verify behavior, this Have EXPLAIN honor debug_print_plan (Tom)
replaces EXPLAIN VERBOSE?
</para> </para>
</listitem> </listitem>
...@@ -1209,11 +1208,11 @@ do it for earlier branch release files. ...@@ -1209,11 +1208,11 @@ do it for earlier branch release files.
<listitem> <listitem>
<para> <para>
Dramatically improve the speed of building and accessing hash indexes Dramatically improve the speed of building and accessing hash indexes
(Tom Raney, Shreya Bhargava, Kenneth Marshall, Tom) (Tom Raney, Shreya Bhargava, Kenneth Marshall)
</para> </para>
<para> <para>
This allows hash indexes to be often faster than btree indexes. This allows hash indexes to be sometimes faster than btree indexes.
However, hash indexes are still not crash-safe. However, hash indexes are still not crash-safe.
</para> </para>
</listitem> </listitem>
...@@ -1810,23 +1809,23 @@ do it for earlier branch release files. ...@@ -1810,23 +1809,23 @@ do it for earlier branch release files.
<itemizedlist> <itemizedlist>
<listitem> <listitem>
<para> <para>
Support DETAIL and HINT fields Support DETAIL and HINT fields
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
Support SQLSTATE error codes Support SQLSTATE error codes
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
Support an exception name parameter Support an exception name parameter
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
Allow RAISE without parameters in an exception Allow RAISE without parameters in an exception
block to rethrow the current error block to rethrow the current error
</para> </para>
</listitem> </listitem>
</itemizedlist> </itemizedlist>
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment