| From: | Jonathan Katz <jonathan(dot)katz(at)excoventures(dot)com> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Press Release Draft - 2016-10-27 Cumulative Update |
| Date: | 2016-10-24 17:14:57 |
| Message-ID: | 70E2E932-BDCC-43B1-BF78-73B464D80499@excoventures.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hello,
Below is the draft of the press release for the update this Thursday:
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>
Per the draft of the release notes, I chose to expand on the data corruption issues after the release summary. I did include the DISTINCT aggregate crashes at the top of the list of fixes but do you think those should be highlighted too?
If you have feedback, please leave it within the next 24 hours (following timeline here: 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>) so I can incorporate it prior to release.
Thanks!
Jonathan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2016-10-24 18:06:55 | Re: FSM corruption leading to errors |
| Previous Message | Pavan Deolasee | 2016-10-24 16:48:07 | Re: FSM corruption leading to errors |