Added details of the major fix a5f0bd77a2fab60a52dc335a63efc21abc806aa7 and also...

diff --git a/update_releases/current/update_201610.md b/update_releases/current/update_201610.md
index 201e8ee72732ec4026a5ea98f8c6b70b7adb55d0..bb98cc8224b89eb0174a197bc7b51746eb28e01a 100644 (file)
--- a/update_releases/current/update_201610.md
+++ b/update_releases/current/update_201610.md
@@ -1,5 +1,5 @@
 2016-10-27 Cumulative Update Release
-==================================
+====================================
 
 The PostgreSQL Global Development Group has released an update to all supported versions of our
 database system, including 9.6.1, 9.5.5, 9.4.10, 9.3.15, 9.2.19, and 9.1.24, where the 9.1 release
@@ -11,10 +11,10 @@ update immediately. Other users should plan to update at the next convenient dow
 {{ SEE http://www.databasesoup.com/2013/10/how-urgent-is-that-update.html }}
 
 WAL-logging of truncated relations
----------------
+----------------------------------
 
-This update fixes around the WAL-logging of truncated relations, which now ensure that the FSM
-is truncated when a TRUNCATE command on a relation is issued, leading to data corruption.  Should
+This update fixes the WAL-logging of truncated relations, which now ensures that the FSM
+is truncated when a TRUNCATE command on a relation is issued, leading to data corruption. Should
 the FSM not be truncated, a PostgreSQL database in recovery mode could return a page that has
 already been truncated and return an error such as:
 
@@ -23,6 +23,20 @@ ERROR:  could not read block 28991 in file "base/16390/572026": read only 0 of 8
 This issue is present in the 9.3, 9.4, 9.5, and 9.6 series of PostgreSQL releases.  
 {{ EXTRA NOTES ON FIX AND COMPATIBILITY ISSUES }}
 
+Fix use-after-free around DISTINCT transition function calls
+------------------------------------------------------------
+
+This fixes a crash when STRING_AGG was used with DISTINCT. It has tuplesort_gettupleslot() copy 
+the contents of its current table slot as needed. This is based on an approach taken by 
+tuplestore_gettupleslot(). In the future, tuplesort_gettupleslot() may also be taught to avoid 
+copying the tuple where caller can determine that that is safe (the tuplestore_gettupleslot() 
+interface already offers this option to callers).
+
+Fix incorrect handling of polymorphic aggregates used as window functions
+-------------------------------------------------------------------------
+
+
+
 Bug Fixes and Improvements
 --------------------------
 
@@ -35,11 +49,12 @@ all supported versions:
 {{ EXTRA NOTES ON SPECIAL ISSUE IF REQUIRED }}
 
 EOL Notice for Version 9.1
------------------------------------------
+--------------------------
 
 PostgreSQL version 9.1 is now End-of-Life (EOL).  No additional updates or security patches
-will be released by the community for this version.  Users still on 9.1
-are urged to upgrade as soon as possible.  See our Versioning Policy for more information.
+will be released by the community for this version.  Users still on 9.1 are urged to upgrade 
+as soon as possible.  See our Versioning Policy (https://www.postgresql.org/support/versioning/) 
+for more information.
 
 Updating
 --------