diff --git a/doc/src/sgml/release-9.2.sgml b/doc/src/sgml/release-9.2.sgml
index 386f28346b9..b62c9e7cdce 100644
--- a/doc/src/sgml/release-9.2.sgml
+++ b/doc/src/sgml/release-9.2.sgml
@@ -7,7 +7,7 @@
Release Date2012-??-??
- CURRENT AS OF 2012-05-09
+ CURRENT AS OF 2012-08-21
@@ -303,10 +303,6 @@
Remove GUC wal_sender_delay>,
as it is no longer needed (Tom Lane)
-
-
- The new "latch" capability made this setting unnecessary.
-
@@ -552,6 +548,20 @@
+
+
+ Improve performance of buffer pool scans that occur when tables or
+ databases are dropped (Jeff Janes, Simon Riggs)
+
+
+
+
+
+ Improve performance of checkpoint process's fsync-request queue
+ when many tables are being dropped or truncated (Tom Lane)
+
+
+
@@ -590,27 +600,16 @@
- Allow backends to detect postmaster death via a pipe read failure,
- rather than polling (Peter Geoghegan, Heikki Linnakangas, Tom Lane)
+ Allow the bgwriter, walwriter, checkpointer, statistics collector, log
+ collector, and archiver background processes to sleep more
+ efficiently during periods of inactivity (Peter Geoghegan, Tom Lane)
- The wait events are internally called "latches".
-
-
-
-
-
- Allow the bgwriter,
- walwriter, statistics collector, archiver,
- and checkpointer to sleep more efficiently during periods of
- inactivity (Peter Geoghegan, Tom Lane)
-
-
-
- This reduces CPU wake-ups, which dramatically
- reduces power consumption on idle servers.
+ This series of changes reduces the frequency of process wake-ups when
+ there is nothing to do, dramatically reducing power consumption on
+ idle servers.
@@ -697,6 +696,13 @@
+
+
+ Account for set-returning functions in SELECT> target
+ lists when setting rowcount estimates (Tom Lane)
+
+
+
@@ -1401,6 +1407,13 @@
This also allows a table to be created whose schema matches a view.
+
+
+
+ Fix CREATE TABLE (LIKE ...) to avoid index name
+ conflicts when copying index comments (Tom Lane)
+
+
@@ -1435,14 +1448,14 @@
- Add support for privileges on date types (Peter Eisentraut)
+ Add support for privileges on data types (Peter Eisentraut)
This adds support for the SQL>-conforming
USAGE> privilege on types and domains. The intent is
- to be able restrict which users can create dependencies on types,
- which restricts the way in which owners can alter types.
+ to be able to restrict which users can create dependencies on types,
+ since such dependencies limit the owner's ability to alter the type.
@@ -1656,7 +1669,7 @@
- Previously only the superuser could use these functions.
+ Previously only superusers could use these functions.
@@ -1927,6 +1940,12 @@
+
+
+ Remove support for Python 2.2 (Peter Eisentraut)
+
+
+
@@ -2317,6 +2336,27 @@
+
+
+ Make pg_dump> emit more useful dependency
+ information (Tom Lane)
+
+
+
+ The dependency links included in archive-format dumps were formerly
+ of very limited use, because they frequently referenced objects that
+ appeared nowhere in the dump. Now they represent actual dependencies
+ (possibly indirect) among the dumped objects.
+
+
+
+
+
+ Improve pg_dump>'s performance when dumping many
+ database objects (Tom Lane)
+
+
+
@@ -2408,6 +2448,17 @@
+
+
+ Remove dead ports (Peter Eisentraut)
+
+
+
+ The following platforms are no longer considered supported: dgux,
+ nextstep, sunos4, svr4, ultrix4, univel, bsdi.
+
+
+
Add support for building with MS
@@ -2428,6 +2479,18 @@
+
+
+ Improve the latch facility to include detection of postmaster death
+ (Peter Geoghegan, Heikki Linnakangas, Tom Lane)
+
+
+
+ This eliminates one of the main reasons that background processes
+ formerly had to wake up to poll for events.
+
+
+
Use C flexible array members, where supported (Peter Eisentraut)
@@ -2520,12 +2583,7 @@
- Remove dead ports (Peter Eisentraut)
-
-
-
- The removed ports are: dgux, nextstep, sunos4, svr4, ultrix4,
- univel, bsdi.
+ Support Linux's /proc/self/oom_score_adj> API (Tom Lane)
@@ -2534,7 +2592,7 @@
- Modules
+ Additional Modules
@@ -2851,6 +2909,19 @@
+
+
+ Deprecate use of GLOBAL> and LOCAL> in
+ CREATE TEMP TABLE> (Noah Misch)
+
+
+
+ PostgreSQL> has long treated these keyword as no-ops,
+ and continues to do so; but in future they might mean what the SQL
+ standard says they mean, so applications should avoid using them.
+
+
+