Re: Press Release Draft - 2016-10-27 Cumulative Update

> On Oct 24, 2016, at 2:59 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> Jonathan Katz <jonathan(dot)katz(at)excoventures(dot)com> writes:
>> 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>
>
> Couple thoughts:
>
> * I don't believe that the FSM truncation issue is specific to being "in
> recovery". The corruption itself would happen during crash/restart on
> a master, or while a standby is following a WAL stream, but the effects
> would be seen later. Suggest just taking out "in recovery" from the
> description.
>
> * Please clarify that the pg_upgrade VM issue is only in 9.6.0.
>
> * The recipe for recovery from the VM issue is oversimplified.
> Rather than trying to explain how to fix it here, I'd suggest
> pointing to the wiki page we've created about that,
> https://wiki.postgresql.org/wiki/Visibility_Map_Problems
>
> Looks good to me otherwise.

Incorporated feedback: https://git.postgresql.org/gitweb/?p=press.git;a=blob;f=update_releases/current/update_201610.md;h=11c9fb9504add6b5c060763722aba1cd2eb4afd4;hb=387f3e441666ce4d2a1e5f4e52247ce3a83e733d <https://git.postgresql.org/gitweb/?p=press.git;a=blob;f=update_releases/current/update_201610.md;h=11c9fb9504add6b5c060763722aba1cd2eb4afd4;hb=387f3e441666ce4d2a1e5f4e52247ce3a83e733d>

Thanks!

Jonathan