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 $ -->
2
2
<!--
3
3
4
4
Typical markup:
@@ -91,14 +91,13 @@ do it for earlier branch release files.
91
91
92
92
<listitem>
93
93
<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
96
95
</para>
97
96
</listitem>
98
97
99
98
<listitem>
100
99
<para>
101
- Updatable cursors using <literal>UPDATE/DELETE WHERE CURRENT OF</>
100
+ Updatable cursors
102
101
</para>
103
102
</listitem>
104
103
@@ -124,17 +123,14 @@ do it for earlier branch release files.
124
123
125
124
<listitem>
126
125
<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
131
127
</para>
132
128
</listitem>
133
129
134
130
<listitem>
135
131
<para>
136
- Support Security Service Provider Interface (SSPI) on
137
- authentication for Windows and GSSAPI
132
+ Support Security Service Provider Interface (<acronym> SSPI</>) for
133
+ authentication on Windows
138
134
</para>
139
135
</listitem>
140
136
@@ -163,8 +159,8 @@ do it for earlier branch release files.
163
159
164
160
<listitem>
165
161
<para>
166
- Asynchronous commit option 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
168
164
</para>
169
165
</listitem>
170
166
@@ -487,8 +483,8 @@ do it for earlier branch release files.
487
483
488
484
<listitem>
489
485
<para>
490
- Asynchronous commit option 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)
492
488
</para>
493
489
494
490
<para>
@@ -526,14 +522,14 @@ do it for earlier branch release files.
526
522
</para>
527
523
528
524
<para>
529
- To allow high concurrency <productname>PostgreSQL </> retains old
530
- versions of updated rows . Previously only <command>VACUUM</>
531
- could reuse space taken by dead 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 is only 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 by old 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 is not possible if
532
+ <command>UPDATE</> changes indexed columns .
537
533
</para>
538
534
</listitem>
539
535
@@ -627,8 +623,9 @@ do it for earlier branch release files.
627
623
</para>
628
624
629
625
<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.
632
629
</para>
633
630
</listitem>
634
631
@@ -694,8 +691,13 @@ do it for earlier branch release files.
694
691
695
692
<listitem>
696
693
<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</>.
699
701
</para>
700
702
</listitem>
701
703
@@ -740,6 +742,10 @@ do it for earlier branch release files.
740
742
Allow logfile creation in CSV format (Arul Shaji, Greg Smith,
741
743
Andrew Dunstan)
742
744
</para>
745
+
746
+ <para>
747
+ The CSV file can be loaded into a database table for analysis.
748
+ </para>
743
749
</listitem>
744
750
745
751
<listitem>
@@ -1004,8 +1010,11 @@ do it for earlier branch release files.
1004
1010
1005
1011
<listitem>
1006
1012
<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</>.
1009
1018
</para>
1010
1019
</listitem>
1011
1020
@@ -1031,8 +1040,9 @@ do it for earlier branch release files.
1031
1040
</para>
1032
1041
1033
1042
<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</>.
1036
1046
</para>
1037
1047
</listitem>
1038
1048
0 commit comments