Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content

Commit 09b68c7

Browse files
committed
One last round of copy-editing for the 9.1 release notes.
Also set the documented release date to 2011-09-12.
1 parent f0bedf3 commit 09b68c7

File tree

1 file changed

+40
-41
lines changed

1 file changed

+40
-41
lines changed

doc/src/sgml/release-9.1.sgml

+40-41
Original file line numberDiff line numberDiff line change
@@ -6,11 +6,9 @@
66

77
<note>
88
<title>Release Date</title>
9-
<simpara>2011-??-??</simpara>
9+
<simpara>2011-09-12</simpara>
1010
</note>
1111

12-
<para>CURRENT AS OF 2011-08-17</para>
13-
1412
<sect2>
1513
<title>Overview</title>
1614

@@ -74,7 +72,7 @@
7472
<listitem>
7573
<para>
7674
Allow data-modification commands
77-
(<command>INSERT</>/<command>UPDATE</>/<command>DELETE)</> in
75+
(<command>INSERT</>/<command>UPDATE</>/<command>DELETE</>) in
7876
<link linkend="queries-with"><literal>WITH</></link> clauses
7977
</para>
8078
</listitem>
@@ -262,7 +260,7 @@
262260
<listitem>
263261
<para>
264262
Require superuser or <literal>CREATEROLE</> permissions in order to
265-
set role comments (Tom Lane)
263+
set comments on roles (Tom Lane)
266264
</para>
267265
</listitem>
268266

@@ -283,8 +281,8 @@
283281
</para>
284282

285283
<para>
286-
Previously <function>pg_last_xlog_receive_location()</> could
287-
move backward when streaming replication is restarted.
284+
Previously, the value of <function>pg_last_xlog_receive_location()</>
285+
could move backward when streaming replication is restarted.
288286
</para>
289287
</listitem>
290288

@@ -296,7 +294,7 @@
296294
</para>
297295

298296
<para>
299-
Previously replication connections were always logged.
297+
Previously, replication connections were always logged.
300298
</para>
301299
</listitem>
302300

@@ -507,8 +505,8 @@
507505
</para>
508506

509507
<para>
510-
This fixes scenarios where backends might hold open files that
511-
were long since deleted, preventing the kernel from reclaiming
508+
This fixes scenarios in which backends might hold files open long
509+
after they were deleted, preventing the kernel from reclaiming
512510
disk space.
513511
</para>
514512
</listitem>
@@ -658,7 +656,7 @@
658656
</para>
659657

660658
<para>
661-
New details show <acronym>WAL</> file and sync activity.
659+
New details include <acronym>WAL</> file and sync activity.
662660
</para>
663661
</listitem>
664662

@@ -757,14 +755,14 @@
757755

758756
<listitem>
759757
<para>
760-
Allow auto-tuning of <link
758+
Provide auto-tuning of <link
761759
linkend="guc-wal-buffers"><varname>wal_buffers</></link> (Greg
762760
Smith)
763761
</para>
764762

765763
<para>
766-
<varname>wal_buffers</> is now auto-tuned by default based on
767-
the size of <varname>shared_buffers</>.
764+
By default, the value of <varname>wal_buffers</> is now chosen
765+
automatically based on the value of <varname>shared_buffers</>.
768766
</para>
769767
</listitem>
770768

@@ -804,8 +802,8 @@
804802
</para>
805803

806804
<para>
807-
This allows the primary to wait for a standby to write the transaction
808-
information to disk before acknowledging the commit.
805+
This allows the primary server to wait for a standby to write a
806+
transaction's information to disk before acknowledging the commit.
809807
One standby at a time can take the role of the synchronous standby,
810808
as controlled by the
811809
<link linkend="guc-synchronous-standby-names"><varname>synchronous_standby_names</varname></link>
@@ -818,8 +816,8 @@
818816

819817
<listitem>
820818
<para>
821-
Add protocol support for sending file system backups to standbys using
822-
the streaming replication network connection (Magnus Hagander,
819+
Add protocol support for sending file system backups to standby servers
820+
using the streaming replication network connection (Magnus Hagander,
823821
Heikki Linnakangas)
824822
</para>
825823

@@ -856,7 +854,7 @@
856854

857855
<listitem>
858856
<para>
859-
Add replication <link linkend="SQL-CREATEROLE">permission</link>
857+
Add a <link linkend="SQL-CREATEROLE">replication permission</link>
860858
for roles (Magnus Hagander)
861859
</para>
862860

@@ -955,7 +953,7 @@
955953
<para>
956954
Increase the maximum values for
957955
<link linkend="guc-max-standby-archive-delay"><varname>max_standby_archive_delay</varname></link> and
958-
<link linkend="guc-max-standby-streaming-delay"><varname>max_standby_streaming_delay</varname></link>.
956+
<link linkend="guc-max-standby-streaming-delay"><varname>max_standby_streaming_delay</varname></link>
959957
</para>
960958

961959
<para>
@@ -1089,7 +1087,7 @@
10891087
Previously, asking for serializable isolation guaranteed only that a
10901088
single MVCC snapshot would be used for the entire transaction, which
10911089
allowed certain documented anomalies. The old snapshot isolation
1092-
behavior is still accessible by requesting the <link
1090+
behavior is still available by requesting the <link
10931091
linkend="xact-repeatable-read"><literal>REPEATABLE READ</></link>
10941092
isolation level.
10951093
</para>
@@ -1098,7 +1096,7 @@
10981096
<listitem>
10991097
<para>
11001098
Allow data-modification commands
1101-
(<command>INSERT</>/<command>UPDATE</>/<command>DELETE)</> in
1099+
(<command>INSERT</>/<command>UPDATE</>/<command>DELETE</>) in
11021100
<link linkend="queries-with"><literal>WITH</></link> clauses
11031101
(Marko Tiikkaja, Hitoshi Harada)
11041102
</para>
@@ -1126,7 +1124,7 @@
11261124
</para>
11271125

11281126
<para>
1129-
Some other database system already allowed this behavior, and
1127+
The SQL standard allows this behavior, and
11301128
because of the primary key, the result is unambiguous.
11311129
</para>
11321130
</listitem>
@@ -1151,9 +1149,9 @@
11511149
</para>
11521150

11531151
<para>
1154-
Previously <command>EXPLAIN ANALYZE</> used a slightly different
1155-
snapshot for queries involving rules. The <command>EXPLAIN ANALYZE</>
1156-
behavior was judged to be more logical.
1152+
Previously <command>EXPLAIN ANALYZE</> used slightly different
1153+
snapshot timing for queries involving rules. The
1154+
<command>EXPLAIN ANALYZE</> behavior was judged to be more logical.
11571155
</para>
11581156
</listitem>
11591157

@@ -1172,7 +1170,8 @@
11721170
</para>
11731171

11741172
<para>
1175-
Previously collation could only be set at database creation.
1173+
Previously collation (the sort ordering of text strings) could only be
1174+
chosen at database creation.
11761175
Collation can now be set per column, domain, index, or
11771176
expression, via the SQL-standard <literal>COLLATE</> clause.
11781177
</para>
@@ -1315,8 +1314,8 @@
13151314
</para>
13161315

13171316
<para>
1318-
The new option is called <literal>NOT VALID</>, which can
1319-
later be modified to <literal>VALIDATED</> and validation
1317+
The new option is called <literal>NOT VALID</>. The constraint's
1318+
state can later be modified to <literal>VALIDATED</> and validation
13201319
checks performed. Together these allow you to add a foreign key
13211320
with minimal impact on read and write operations.
13221321
</para>
@@ -1352,14 +1351,14 @@
13521351
<listitem>
13531352
<para>
13541353
Fix possible <quote>tuple concurrently updated</quote> error
1355-
when two backends attempted to add an inheritance
1354+
when two backends attempt to add an inheritance
13561355
child to the same table at the same time (Robert Haas)
13571356
</para>
13581357

13591358
<para>
13601359
<link linkend="sql-altertable"><command>ALTER TABLE</command></link>
1361-
now takes a stronger lock on the parent table, so that both children do
1362-
not try to update it simultaneously.
1360+
now takes a stronger lock on the parent table, so that the sessions
1361+
cannot try to update it simultaneously.
13631362
</para>
13641363
</listitem>
13651364

@@ -1401,8 +1400,8 @@
14011400
</para>
14021401

14031402
<para>
1404-
This is similar to the existing session-level advisory locks,
1405-
but the locks are automatically released at transaction end.
1403+
These are similar to the existing session-level advisory locks,
1404+
but such locks are automatically released at transaction end.
14061405
</para>
14071406
</listitem>
14081407

@@ -1599,7 +1598,7 @@ SELECT * FROM places ORDER BY location <-> point '(101,456)' LIMIT 10;
15991598

16001599
<para>
16011600
Previously all <type>numeric</> values had four-byte headers;
1602-
this saves on disk storage.
1601+
this change saves on disk storage.
16031602
</para>
16041603
</listitem>
16051604

@@ -1667,7 +1666,7 @@ SELECT * FROM places ORDER BY location <-> point '(101,456)' LIMIT 10;
16671666
<listitem>
16681667
<para>
16691668
Add support for casting from <type>int4</> and <type>int8</>
1670-
to <type>numeric</> (Joey Adams)
1669+
to <type>money</> (Joey Adams)
16711670
</para>
16721671
</listitem>
16731672

@@ -1737,9 +1736,9 @@ SELECT * FROM places ORDER BY location <-> point '(101,456)' LIMIT 10;
17371736
<listitem>
17381737
<para>
17391738
Add SQL function <link
1740-
linkend="format"><function>format(text)</></link>, which
1741-
behaves like C's <function>printf()</> (Pavel Stehule, Robert
1742-
Haas)
1739+
linkend="format"><function>format(text, ...)</></link>, which
1740+
behaves analogously to C's <function>printf()</> (Pavel Stehule,
1741+
Robert Haas)
17431742
</para>
17441743

17451744
<para>
@@ -2027,7 +2026,7 @@ SELECT * FROM places ORDER BY location <-> point '(101,456)' LIMIT 10;
20272026
</para>
20282027

20292028
<para>
2030-
The functions are <link
2029+
These functions are <link
20312030
linkend="plpython-util"><literal>plpy.quote_ident</></link>,
20322031
<link linkend="plpython-util"><literal>plpy.quote_literal</></link>,
20332032
and <link
@@ -2605,7 +2604,7 @@ SELECT * FROM places ORDER BY location <-> point '(101,456)' LIMIT 10;
26052604

26062605
<listitem>
26072606
<para>
2608-
Modify <filename>contrib</> modules and stored procedure
2607+
Modify <filename>contrib</> modules and procedural
26092608
languages to install via the new <link
26102609
linkend="extend-extensions">extension</link> mechanism (Tom Lane,
26112610
Dimitri Fontaine)

0 commit comments

Comments
 (0)