Re: volunteer to draft next update release

> On Oct 24, 2016, at 12:40 PM, Josh Berkus <josh(at)agliodbs(dot)com> wrote:
> Suggested change in first paragraph:
>
> "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. This is also the last update for
> ^^^^^^^^
> the PostgreSQL 9.1 series as it is now end-of-life. This release fixes
> two issues that can cause data corruption, which are described in more
> detail below. It also patches a number of other bugs reported over the
> last three months."
>
> This part is confusing to me:
>
> "Users who are affected by the data corruption issues should update
> immediately. Other users should plan to update at the next convenient
> downtime."
>
> So ... the WAL-logging issue affects everyone on 9.3 or later, which is
> most users reading the update releases. However, it can't be that
> common or we'd have gotten bug reports on it more frequently. The big
> endian issue is new and severe. I might suggest instead:
>
> "The project urges users to apply this update at the next possible
> downtime."
>
> ... since it's really only 9.1/9.2 users on Intel who are unaffected by
> either issue, and we want 9.1 users to upgrade anyway. Users can opt out
> if they think it doesn't affect them.
>
> Otherwise, looks great.

Cool - thank you. I have incorporated the feedback here:

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>

Will message to -hackers.

Thanks,

Jonathan