On Wed, Oct 19, 2016 at 11:47:51AM -0400, Jonathan S. Katz wrote:
> Answer is yes.
>
> Because this is my first time doing this, I want to work on it early and often
> to get into the proper cadence :-) I took a try at writing up the data
> corruption issue as well as adding the EOL language:
>
> https://git.postgresql.org/gitweb/?p=press.git;a=commitdiff;h=
> 38aadd18e9c64f30423f81920381b001fff8b4c5;hp=
> 1ada1db63eaed94e499c1289e90bdf70a47f9fc0
>
> I understand part of the challenge is taking the detailed commit notes and
> putting it into language that makes sense to the users, which is why I want
> more eyes on this. I intend to fill out more details once the rest of the
> release notes are out, but if there are major issues I find it prudent that we
> get the language for that correct so users understand the ramifications and the
> need to upgrade.
Yes, this is a wise approach as things like special upgrade instructions
are often not in the release notes, e.g. fixing visibility map
corruption when upgrading to 9.6.1 for big-endian systems.
--
Bruce Momjian <bruce@momjian.us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +
