Do we need to add anything in the release notes about possible
complications in upgrading caused by the 65f39408ee71 / 56535dcdc9e2
issue?
If upgrading from the immediately prior point releases to this one, then
the shutdown of the previous version might have left an incorrect min
recovery point in pg_control, yes? So the error could then occur when
starting the new version, even though the bug is now apparently fixed.
--
Andrew (irc:RhodiumToad)