1- <!-- $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.528 2007/10/19 01:56:06 momjian Exp $ -->
1+ <!-- $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.529 2007/10/20 16:41:09 momjian Exp $ -->
22<!--
33
44Typical markup:
@@ -91,14 +91,13 @@ do it for earlier branch release files.
9191
9292 <listitem>
9393 <para>
94- Control over whether <literal>NULL</>s sort first or last, using
95- <literal>ORDER BY ... NULLS FIRST/LAST</>
94+ Control over whether <literal>NULL</>s sort first or last
9695 </para>
9796 </listitem>
9897
9998 <listitem>
10099 <para>
101- Updatable cursors using <literal>UPDATE/DELETE WHERE CURRENT OF</>
100+ Updatable cursors
102101 </para>
103102 </listitem>
104103
@@ -124,17 +123,14 @@ do it for earlier branch release files.
124123
125124 <listitem>
126125 <para>
127- Numerous improvements in logging and statistics collection,
128- including the ability to emit postmaster log messages in
129- <acronym>CSV</> format, which can be loaded into a database
130- table for analysis
126+ Numerous improvements in logging and statistics collection
131127 </para>
132128 </listitem>
133129
134130 <listitem>
135131 <para>
136- Support Security Service Provider Interface (SSPI) on
137- authenticationfor Windows and GSSAPI
132+ Support Security Service Provider Interface (<acronym> SSPI</>) for
133+ authenticationon Windows
138134 </para>
139135 </listitem>
140136
@@ -163,8 +159,8 @@ do it for earlier branch release files.
163159
164160 <listitem>
165161 <para>
166- Asynchronous commitoption allows transactions to be committed
167- but on-disk changes to be delayed
162+ Asynchronous commit allows transactions to be committed but on-disk
163+ changes to be delayed
168164 </para>
169165 </listitem>
170166
@@ -487,8 +483,8 @@ do it for earlier branch release files.
487483
488484 <listitem>
489485 <para>
490- Asynchronous commitoption allows transactions to be committed
491- but on-disk changes to be delayed (Simon)
486+ Asynchronous commit allows transactions to be committed but on-disk
487+ changes to be delayed (Simon)
492488 </para>
493489
494490 <para>
@@ -526,14 +522,14 @@ do it for earlier branch release files.
526522 </para>
527523
528524 <para>
529- To allow high concurrency <productname>PostgreSQL </>retains old
530- versions of updated rows . Previously only <command>VACUUM</>
531- could reuse space taken bydead rows . With <acronym>HOT</> dead
532- row space can be reused at the time of <command>UPDATE</> or
533- <command>INSERT</>. This allows for more consistent performance.
534- <acronym>HOT</> even allows deleted row space reuse.
535- <command>UPDATE </> space reuse isonly possible if no modified
536- columns are indexed.
525+ To allow high concurrency <command>UPDATE </>creates a new tuple,
526+ rather than replacing the old tuple . Previously only
527+ <command>VACUUM</> could reuse space taken byold tuples . With
528+ <acronym>HOT</> dead tuple space can be reused at the time of
529+ <command>UPDATE</> or <command> INSERT</>. This allows for more
530+ consistent performance. <acronym>HOT</> even allows deleted row
531+ space reuse. <acronym>HOT </> space reuse isnot possible if
532+ <command>UPDATE</> changes indexed columns .
537533 </para>
538534 </listitem>
539535
@@ -627,8 +623,9 @@ do it for earlier branch release files.
627623 </para>
628624
629625 <para>
630- This is done by scanning the table and using a filter to save
631- the few requested rows, rather than sorting the entire table.
626+ This is done by sequentially scanning the table and using a filter
627+ to save the few requested rows, rather than sorting the entire
628+ table. This is used if there is no matching index.
632629 </para>
633630 </listitem>
634631
@@ -694,8 +691,13 @@ do it for earlier branch release files.
694691
695692 <listitem>
696693 <para>
697- Support Security Service Provider Interface (SSPI)
698- authentication on Windows (Magnus)
694+ Support Security Service Provider Interface (<acronym>SSPI</>) for
695+ authentication on Windows
696+ </para>
697+
698+ <para>
699+ This also adds support for the <acryonym>GSSAPI</> authentication
700+ <acronym>API</>.
699701 </para>
700702 </listitem>
701703
@@ -740,6 +742,10 @@ do it for earlier branch release files.
740742 Allow logfile creation in CSV format (Arul Shaji, Greg Smith,
741743 Andrew Dunstan)
742744 </para>
745+
746+ <para>
747+ The CSV file can be loaded into a database table for analysis.
748+ </para>
743749 </listitem>
744750
745751 <listitem>
@@ -1004,8 +1010,11 @@ do it for earlier branch release files.
10041010
10051011 <listitem>
10061012 <para>
1007- Control over whether <literal>NULL</>s sort first or last, using
1008- <literal>ORDER BY ... NULLS FIRST/LAST</> (Teodor, Tom)
1013+ Control over whether <literal>NULL</>s sort first or last (Teodor, Tom)
1014+ </para>
1015+
1016+ <para>
1017+ The syntax is <literal>ORDER BY ... NULLS FIRST/LAST</>.
10091018 </para>
10101019 </listitem>
10111020
@@ -1031,8 +1040,9 @@ do it for earlier branch release files.
10311040 </para>
10321041
10331042 <para>
1034- This eliminates the need to reference a primary key to update or
1035- delete rows returned by a cursor.
1043+ This eliminates the need to reference a primary key to
1044+ <command>UPDATE</> or <command>DELETE</> rows returned by a cursor.
1045+ The syntax is <literal>UPDATE/DELETE WHERE CURRENT OF</>.
10361046 </para>
10371047 </listitem>
10381048