|
6 | 6 |
|
7 | 7 | <note>
|
8 | 8 | <title>Release Date</title>
|
9 |
| - <simpara>2011-??-??</simpara> |
| 9 | + <simpara>2011-09-12</simpara> |
10 | 10 | </note>
|
11 | 11 |
|
12 |
| - <para>CURRENT AS OF 2011-08-17</para> |
13 |
| - |
14 | 12 | <sect2>
|
15 | 13 | <title>Overview</title>
|
16 | 14 |
|
|
74 | 72 | <listitem>
|
75 | 73 | <para>
|
76 | 74 | Allow data-modification commands
|
77 |
| - (<command>INSERT</>/<command>UPDATE</>/<command>DELETE)</> in |
| 75 | + (<command>INSERT</>/<command>UPDATE</>/<command>DELETE</>) in |
78 | 76 | <link linkend="queries-with"><literal>WITH</></link> clauses
|
79 | 77 | </para>
|
80 | 78 | </listitem>
|
|
262 | 260 | <listitem>
|
263 | 261 | <para>
|
264 | 262 | Require superuser or <literal>CREATEROLE</> permissions in order to
|
265 |
| - set role comments (Tom Lane) |
| 263 | + set comments on roles (Tom Lane) |
266 | 264 | </para>
|
267 | 265 | </listitem>
|
268 | 266 |
|
|
283 | 281 | </para>
|
284 | 282 |
|
285 | 283 | <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. |
288 | 286 | </para>
|
289 | 287 | </listitem>
|
290 | 288 |
|
|
296 | 294 | </para>
|
297 | 295 |
|
298 | 296 | <para>
|
299 |
| - Previously replication connections were always logged. |
| 297 | + Previously, replication connections were always logged. |
300 | 298 | </para>
|
301 | 299 | </listitem>
|
302 | 300 |
|
|
507 | 505 | </para>
|
508 | 506 |
|
509 | 507 | <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 |
512 | 510 | disk space.
|
513 | 511 | </para>
|
514 | 512 | </listitem>
|
|
658 | 656 | </para>
|
659 | 657 |
|
660 | 658 | <para>
|
661 |
| - New details show <acronym>WAL</> file and sync activity. |
| 659 | + New details include <acronym>WAL</> file and sync activity. |
662 | 660 | </para>
|
663 | 661 | </listitem>
|
664 | 662 |
|
|
757 | 755 |
|
758 | 756 | <listitem>
|
759 | 757 | <para>
|
760 |
| - Allow auto-tuning of <link |
| 758 | + Provide auto-tuning of <link |
761 | 759 | linkend="guc-wal-buffers"><varname>wal_buffers</></link> (Greg
|
762 | 760 | Smith)
|
763 | 761 | </para>
|
764 | 762 |
|
765 | 763 | <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</>. |
768 | 766 | </para>
|
769 | 767 | </listitem>
|
770 | 768 |
|
|
804 | 802 | </para>
|
805 | 803 |
|
806 | 804 | <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. |
809 | 807 | One standby at a time can take the role of the synchronous standby,
|
810 | 808 | as controlled by the
|
811 | 809 | <link linkend="guc-synchronous-standby-names"><varname>synchronous_standby_names</varname></link>
|
|
818 | 816 |
|
819 | 817 | <listitem>
|
820 | 818 | <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, |
823 | 821 | Heikki Linnakangas)
|
824 | 822 | </para>
|
825 | 823 |
|
|
856 | 854 |
|
857 | 855 | <listitem>
|
858 | 856 | <para>
|
859 |
| - Add replication <link linkend="SQL-CREATEROLE">permission</link> |
| 857 | + Add a <link linkend="SQL-CREATEROLE">replication permission</link> |
860 | 858 | for roles (Magnus Hagander)
|
861 | 859 | </para>
|
862 | 860 |
|
|
955 | 953 | <para>
|
956 | 954 | Increase the maximum values for
|
957 | 955 | <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> |
959 | 957 | </para>
|
960 | 958 |
|
961 | 959 | <para>
|
|
1089 | 1087 | Previously, asking for serializable isolation guaranteed only that a
|
1090 | 1088 | single MVCC snapshot would be used for the entire transaction, which
|
1091 | 1089 | 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 |
1093 | 1091 | linkend="xact-repeatable-read"><literal>REPEATABLE READ</></link>
|
1094 | 1092 | isolation level.
|
1095 | 1093 | </para>
|
|
1098 | 1096 | <listitem>
|
1099 | 1097 | <para>
|
1100 | 1098 | Allow data-modification commands
|
1101 |
| - (<command>INSERT</>/<command>UPDATE</>/<command>DELETE)</> in |
| 1099 | + (<command>INSERT</>/<command>UPDATE</>/<command>DELETE</>) in |
1102 | 1100 | <link linkend="queries-with"><literal>WITH</></link> clauses
|
1103 | 1101 | (Marko Tiikkaja, Hitoshi Harada)
|
1104 | 1102 | </para>
|
|
1126 | 1124 | </para>
|
1127 | 1125 |
|
1128 | 1126 | <para>
|
1129 |
| - Some other database system already allowed this behavior, and |
| 1127 | + The SQL standard allows this behavior, and |
1130 | 1128 | because of the primary key, the result is unambiguous.
|
1131 | 1129 | </para>
|
1132 | 1130 | </listitem>
|
|
1151 | 1149 | </para>
|
1152 | 1150 |
|
1153 | 1151 | <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. |
1157 | 1155 | </para>
|
1158 | 1156 | </listitem>
|
1159 | 1157 |
|
|
1172 | 1170 | </para>
|
1173 | 1171 |
|
1174 | 1172 | <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. |
1176 | 1175 | Collation can now be set per column, domain, index, or
|
1177 | 1176 | expression, via the SQL-standard <literal>COLLATE</> clause.
|
1178 | 1177 | </para>
|
|
1315 | 1314 | </para>
|
1316 | 1315 |
|
1317 | 1316 | <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 |
1320 | 1319 | checks performed. Together these allow you to add a foreign key
|
1321 | 1320 | with minimal impact on read and write operations.
|
1322 | 1321 | </para>
|
|
1352 | 1351 | <listitem>
|
1353 | 1352 | <para>
|
1354 | 1353 | 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 |
1356 | 1355 | child to the same table at the same time (Robert Haas)
|
1357 | 1356 | </para>
|
1358 | 1357 |
|
1359 | 1358 | <para>
|
1360 | 1359 | <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. |
1363 | 1362 | </para>
|
1364 | 1363 | </listitem>
|
1365 | 1364 |
|
|
1401 | 1400 | </para>
|
1402 | 1401 |
|
1403 | 1402 | <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. |
1406 | 1405 | </para>
|
1407 | 1406 | </listitem>
|
1408 | 1407 |
|
@@ -1599,7 +1598,7 @@ SELECT * FROM places ORDER BY location <-> point '(101,456)' LIMIT 10;
|
1599 | 1598 |
|
1600 | 1599 | <para>
|
1601 | 1600 | Previously all <type>numeric</> values had four-byte headers;
|
1602 |
| - this saves on disk storage. |
| 1601 | + this change saves on disk storage. |
1603 | 1602 | </para>
|
1604 | 1603 | </listitem>
|
1605 | 1604 |
|
@@ -1667,7 +1666,7 @@ SELECT * FROM places ORDER BY location <-> point '(101,456)' LIMIT 10;
|
1667 | 1666 | <listitem>
|
1668 | 1667 | <para>
|
1669 | 1668 | Add support for casting from <type>int4</> and <type>int8</>
|
1670 |
| - to <type>numeric</> (Joey Adams) |
| 1669 | + to <type>money</> (Joey Adams) |
1671 | 1670 | </para>
|
1672 | 1671 | </listitem>
|
1673 | 1672 |
|
@@ -1737,9 +1736,9 @@ SELECT * FROM places ORDER BY location <-> point '(101,456)' LIMIT 10;
|
1737 | 1736 | <listitem>
|
1738 | 1737 | <para>
|
1739 | 1738 | 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) |
1743 | 1742 | </para>
|
1744 | 1743 |
|
1745 | 1744 | <para>
|
@@ -2027,7 +2026,7 @@ SELECT * FROM places ORDER BY location <-> point '(101,456)' LIMIT 10;
|
2027 | 2026 | </para>
|
2028 | 2027 |
|
2029 | 2028 | <para>
|
2030 |
| - The functions are <link |
| 2029 | + These functions are <link |
2031 | 2030 | linkend="plpython-util"><literal>plpy.quote_ident</></link>,
|
2032 | 2031 | <link linkend="plpython-util"><literal>plpy.quote_literal</></link>,
|
2033 | 2032 | and <link
|
@@ -2605,7 +2604,7 @@ SELECT * FROM places ORDER BY location <-> point '(101,456)' LIMIT 10;
|
2605 | 2604 |
|
2606 | 2605 | <listitem>
|
2607 | 2606 | <para>
|
2608 |
| - Modify <filename>contrib</> modules and stored procedure |
| 2607 | + Modify <filename>contrib</> modules and procedural |
2609 | 2608 | languages to install via the new <link
|
2610 | 2609 | linkend="extend-extensions">extension</link> mechanism (Tom Lane,
|
2611 | 2610 | Dimitri Fontaine)
|
|
0 commit comments