-{{ DATE_HERE }} Cumulative Update Release
+2016-10-27 Cumulative Update Release
==================================
-The PostgreSQL Global Development Group has released an update to all supported versions of our database system, including {{ LIST OF MINOR VERSIONS }}. This release fixes {{ 1-3 BIGGEST ISSUES }}. It also patches a number of other bugs reported over the last three months.
-{{ %IF MAJOR_ISSUE AFFECTS ONLY SOME USERS }}
-Users who are affected by {{ MAJOR ISSUE }} should update as soon as possible. Other users should plan to update at the next convenient downtime.
-{{ %ELSEIF MAJOR_ISSUE AFFECTS MOST USERS }}
-Users of {{ AFFECTED_VERSIONS }} should plan to update {{ immediately | as soon as possible | at the next available opportunity }}
-{{ %ELSE }}
-Users should plan to apply this update at the next scheduled downtime.
-{{ %ENDIF }}
+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
+is the last release for PostgreSQL version 9.1. This release fixes a WAL logging issue for
+truncated relations that can lead to data corruption. It also patches a number of other bugs
+reported over the last three months. Users who are affected by the data corruption issues should
+update immediately. Other users should plan to update at the next convenient downtime.
+
{{ SEE http://www.databasesoup.com/2013/10/how-urgent-is-that-update.html }}
-{{ MAJOR_ISSUE }}
+WAL-logging of truncated relations
---------------
-This update fixes {{ MAJOR_ISSUE }}, which {{ DESCRIPTION OF ISSUE }}.
+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
+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:
+
+ERROR: could not read block 28991 in file "base/16390/572026": read only 0 of 8192 bytes
+
+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 }}
Bug Fixes and Improvements
{{ EXTRA NOTES ON SPECIAL ISSUE IF REQUIRED }}
-This update also contains tzdata release {{ TZDATA_RELEASE }},
-with updates for {{ LIST OF TIME ZONES }}.
-
-{{ %IF 2 to 5 MONTHS FROM EOL }}
-EOL Warning for Version {{ EOL VERSION }}
+EOL Notice for Version 9.1
-----------------------------------------
-PostgreSQL version {{ EOL VERSION }} will be End-of-Life in {{ MONTH YEAR }}. The project expects to only release one more update for that version. We urge users to start planning an upgrade to a later version of PostgreSQL as soon as possible. See our Versioning Policy for more information.
-
-{{ %ENDIF }}
-
-{{ %IF 0 to 1 MONTHS FROM EOL }}
-EOL Notice for Version {{ EOL VERSION }}
------------------------------------------
-
-PostgreSQL version {{ EOL VERSION }} is now End-of-Life (EOL). No additional updates or security patches
-will be released by the community for this version. Users still on {{ EOL VERSION }}
+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.
-{{ %ENDIF }}
-
Updating
--------