Update 9.6 release notes through today.

diff --git a/doc/src/sgml/release-9.6.sgml b/doc/src/sgml/release-9.6.sgml
index 230eb4cb4c06629d20c35c8e93befe81ae7f1877..22379b9da6111227bffa4d2e86dee891c389c076 100644 (file)
--- a/doc/src/sgml/release-9.6.sgml
+++ b/doc/src/sgml/release-9.6.sgml
@@ -7,7 +7,7 @@
   
    Release Date
    2016-??-??
-   Current as of 2016-07-16 (commit 606ccc5e7)
+   Current as of 2016-08-07 (commit 19322c0a7)
   
 
   
@@ -259,10 +259,12 @@
 2016-03-10 [fd31cd265] Don't vacuum all-frozen pages.
 2016-03-11 [7087166a8] pg_upgrade: Convert old visibility map format to new for
 2016-06-17 [ede62e56f] Add VACUUM (DISABLE_PAGE_SKIPPING) for emergencies.
+2016-07-18 [eca0f1db1] Clear all-frozen visibilitymap status when locking tuple
+2016-08-04 [e7caacf73] Fix hard to hit race condition in heapam's tuple locking
 -->
        
         Avoid re-vacuuming pages containing only frozen tuples
-        (Masahiko Sawada, Robert Haas)
+        (Masahiko Sawada, Robert Haas, Andres Freund)
        
 
        
@@ -419,6 +421,8 @@
 2016-04-08 [848ef42bb] Add the "snapshot too old" feature
 2016-05-06 [2cc41acd8] Fix hash index vs "snapshot too old" problemms
 2016-05-06 [7e3da1c47] Mitigate "snapshot too old" performance regression on NU
+2016-08-03 [3e2f3c2e4] Prevent "snapshot too old" from trying to return pruned
+2016-08-07 [9ee1cf04a] Fix TOAST access failure in RETURNING queries.
 -->
        
         Allow old MVCC snapshots to be invalidated after a configurable
@@ -1295,6 +1299,41 @@ XXX this is pending backpatch, may need to remove
 
       
 
+       
+        Allow functions that return sets of tuples to return simple NULLs
+        (Andrew Gierth, Tom Lane)
+       
+
+       
+        In the context of SELECT FROM function(...), a function
+        that returned a set of composite values was previously not allowed
+        to return a plain NULL value as part of the set.  Now that is
+        allowed and interpreted as a row of NULLs.  This avoids corner-case
+        errors with, for example, unnesting an array of composite values.
+       
+      
+
+      
+
+       
+        Fully support array subscripts and field selections in the target
+        column list of an INSERT with
+        multiple VALUES rows (Tom Lane)
+       
+
+       
+        Previously, such cases failed if the same target column was
+        mentioned more than once, e.g., INSERT INTO tab (x[1],
+        x[2]) VALUES ....
+       
+      
+
+      
+
@@ -2041,6 +2080,42 @@ XXX this is pending backpatch, may need to remove
        
       
 
+      
+
+       
+        Change various catalog-inspection functions to return NULL for
+        invalid input (Michael Paquier)
+       
+
+       
+        pg_get_viewdef() now returns NULL if given an invalid
+        view OID, and several similar functions likewise return NULL for
+        bad input.  Previously, such cases usually led to cache
+        lookup failed errors, which are not meant to occur in
+        user-facing cases.
+       
+      
+
+      
+
+       
+        Fix pg_replication_origin_xact_reset() to not have any
+        arguments (Fujii Masao)
+       
+
+       
+        The documentation said that it has no arguments, and the C code
+        didn't expect any arguments, but the entry in pg_proc
+        mistakenly specified two arguments.
+       
+      
+