More release note wording improvements.
This commit is contained in:
parent
7b98f6be6e
commit
1ba96ef04f
@ -1,4 +1,4 @@
|
|||||||
<!-- $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.528 2007/10/19 01:56:06 momjian Exp $ -->
|
<!-- $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.529 2007/10/20 16:41:09 momjian Exp $ -->
|
||||||
<!--
|
<!--
|
||||||
|
|
||||||
Typical markup:
|
Typical markup:
|
||||||
@ -91,14 +91,13 @@ do it for earlier branch release files.
|
|||||||
|
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>
|
<para>
|
||||||
Control over whether <literal>NULL</>s sort first or last, using
|
Control over whether <literal>NULL</>s sort first or last
|
||||||
<literal>ORDER BY ... NULLS FIRST/LAST</>
|
|
||||||
</para>
|
</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
|
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>
|
<para>
|
||||||
Updatable cursors using <literal>UPDATE/DELETE WHERE CURRENT OF</>
|
Updatable cursors
|
||||||
</para>
|
</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
|
|
||||||
@ -124,17 +123,14 @@ do it for earlier branch release files.
|
|||||||
|
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>
|
<para>
|
||||||
Numerous improvements in logging and statistics collection,
|
Numerous improvements in logging and statistics collection
|
||||||
including the ability to emit postmaster log messages in
|
|
||||||
<acronym>CSV</> format, which can be loaded into a database
|
|
||||||
table for analysis
|
|
||||||
</para>
|
</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
|
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>
|
<para>
|
||||||
Support Security Service Provider Interface (SSPI) on
|
Support Security Service Provider Interface (<acronym>SSPI</>) for
|
||||||
authentication for Windows and GSSAPI
|
authentication on Windows
|
||||||
</para>
|
</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
|
|
||||||
@ -163,8 +159,8 @@ do it for earlier branch release files.
|
|||||||
|
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>
|
<para>
|
||||||
Asynchronous commit option allows transactions to be committed
|
Asynchronous commit allows transactions to be committed but on-disk
|
||||||
but on-disk changes to be delayed
|
changes to be delayed
|
||||||
</para>
|
</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
|
|
||||||
@ -487,8 +483,8 @@ do it for earlier branch release files.
|
|||||||
|
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>
|
<para>
|
||||||
Asynchronous commit option allows transactions to be committed
|
Asynchronous commit allows transactions to be committed but on-disk
|
||||||
but on-disk changes to be delayed (Simon)
|
changes to be delayed (Simon)
|
||||||
</para>
|
</para>
|
||||||
|
|
||||||
<para>
|
<para>
|
||||||
@ -526,14 +522,14 @@ do it for earlier branch release files.
|
|||||||
</para>
|
</para>
|
||||||
|
|
||||||
<para>
|
<para>
|
||||||
To allow high concurrency <productname>PostgreSQL</> retains old
|
To allow high concurrency <command>UPDATE</> creates a new tuple,
|
||||||
versions of updated rows. Previously only <command>VACUUM</>
|
rather than replacing the old tuple. Previously only
|
||||||
could reuse space taken by dead rows. With <acronym>HOT</> dead
|
<command>VACUUM</> could reuse space taken by old tuples. With
|
||||||
row space can be reused at the time of <command>UPDATE</> or
|
<acronym>HOT</> dead tuple space can be reused at the time of
|
||||||
<command>INSERT</>. This allows for more consistent performance.
|
<command>UPDATE</> or <command>INSERT</>. This allows for more
|
||||||
<acronym>HOT</> even allows deleted row space reuse.
|
consistent performance. <acronym>HOT</> even allows deleted row
|
||||||
<command>UPDATE</> space reuse is only possible if no modified
|
space reuse. <acronym>HOT</> space reuse is not possible if
|
||||||
columns are indexed.
|
<command>UPDATE</> changes indexed columns.
|
||||||
</para>
|
</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
|
|
||||||
@ -627,8 +623,9 @@ do it for earlier branch release files.
|
|||||||
</para>
|
</para>
|
||||||
|
|
||||||
<para>
|
<para>
|
||||||
This is done by scanning the table and using a filter to save
|
This is done by sequentially scanning the table and using a filter
|
||||||
the few requested rows, rather than sorting the entire table.
|
to save the few requested rows, rather than sorting the entire
|
||||||
|
table. This is used if there is no matching index.
|
||||||
</para>
|
</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
|
|
||||||
@ -694,8 +691,13 @@ do it for earlier branch release files.
|
|||||||
|
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>
|
<para>
|
||||||
Support Security Service Provider Interface (SSPI)
|
Support Security Service Provider Interface (<acronym>SSPI</>) for
|
||||||
authentication on Windows (Magnus)
|
authentication on Windows
|
||||||
|
</para>
|
||||||
|
|
||||||
|
<para>
|
||||||
|
This also adds support for the <acryonym>GSSAPI</> authentication
|
||||||
|
<acronym>API</>.
|
||||||
</para>
|
</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
|
|
||||||
@ -740,6 +742,10 @@ do it for earlier branch release files.
|
|||||||
Allow logfile creation in CSV format (Arul Shaji, Greg Smith,
|
Allow logfile creation in CSV format (Arul Shaji, Greg Smith,
|
||||||
Andrew Dunstan)
|
Andrew Dunstan)
|
||||||
</para>
|
</para>
|
||||||
|
|
||||||
|
<para>
|
||||||
|
The CSV file can be loaded into a database table for analysis.
|
||||||
|
</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
|
|
||||||
<listitem>
|
<listitem>
|
||||||
@ -1004,8 +1010,11 @@ do it for earlier branch release files.
|
|||||||
|
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>
|
<para>
|
||||||
Control over whether <literal>NULL</>s sort first or last, using
|
Control over whether <literal>NULL</>s sort first or last (Teodor, Tom)
|
||||||
<literal>ORDER BY ... NULLS FIRST/LAST</> (Teodor, Tom)
|
</para>
|
||||||
|
|
||||||
|
<para>
|
||||||
|
The syntax is <literal>ORDER BY ... NULLS FIRST/LAST</>.
|
||||||
</para>
|
</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
|
|
||||||
@ -1031,8 +1040,9 @@ do it for earlier branch release files.
|
|||||||
</para>
|
</para>
|
||||||
|
|
||||||
<para>
|
<para>
|
||||||
This eliminates the need to reference a primary key to update or
|
This eliminates the need to reference a primary key to
|
||||||
delete rows returned by a cursor.
|
<command>UPDATE</> or <command>DELETE</> rows returned by a cursor.
|
||||||
|
The syntax is <literal>UPDATE/DELETE WHERE CURRENT OF</>.
|
||||||
</para>
|
</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
|
|
||||||
|
Loading…
x
Reference in New Issue
Block a user