| From: | Stephen Frost <sfrost(at)snowman(dot)net> |
|---|---|
| To: | Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)lists(dot)postgresql(dot)org, Andres Freund <andres(at)anarazel(dot)de>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Subject: | Re: First-draft release notes for back-branch releases |
| Date: | 2018-11-06 22:17:43 |
| Message-ID: | 20181106221743.GI18594@tamriel.snowman.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Greetings,
* Andrew Gierth (andrew(at)tao11(dot)riddles(dot)org(dot)uk) wrote:
> 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.
Based on the discussion on IRC and Andrew's comments above, it seems to
me like we should really highlight this. Would be nice if we could
include some information about what to do if someone is bit by this
also...
Thanks!
Stephen
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jonathan S. Katz | 2018-11-06 22:17:48 | Re: First-draft release notes for back-branch releases |
| Previous Message | Simon Riggs | 2018-11-06 22:17:10 | Re: [HACKERS] generated columns |