Press Release Draft - 2016-10-27 Cumulative Update - Mailing list pgsql-hackers

<div class="">Hello,</div><div class=""><br class="" /></div><div class="">Below is the draft of the press release for
theupdate this Thursday:</div><div class=""><br class="" /></div><div class=""><a class=""
href="https://git.postgresql.org/gitweb/?p=press.git;a=blob;f=update_releases/current/update_201610.md;h=aac4d0b36f3f3017d319ac617eff901efe0c10c0;hb=880dc99766ee0e608e95d9c0f36ce3cde59f470f">https://git.postgresql.org/gitweb/?p=press.git;a=blob;f=update_releases/current/update_201610.md;h=aac4d0b36f3f3017d319ac617eff901efe0c10c0;hb=880dc99766ee0e608e95d9c0f36ce3cde59f470f</a></div><div
class=""><brclass="" /></div><div class="">Per the draft of the release notes, I chose to expand on the data corruption
issuesafter the release summary.  I did include the DISTINCT aggregate crashes at the top of the list of fixes but do
youthink those should be highlighted too?</div><div class=""><br class="" /></div><div class="">If you have feedback,
pleaseleave it within the next 24 hours (following timeline here: <a class=""
href="https://wiki.postgresql.org/wiki/UpdateReleaseDrafting#Tuesday_Night_or_Wednesday_Morning_.28US_Time.29">https://wiki.postgresql.org/wiki/UpdateReleaseDrafting#Tuesday_Night_or_Wednesday_Morning_.28US_Time.29</a>)
soI can incorporate it prior to release.</div><div class=""><br class="" /></div><div class="">Thanks!</div><div
class=""><brclass="" /></div><div class="">Jonathan</div>