From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | David Gould <daveg(at)sonic(dot)net> |
Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, pgsql-core <pgsql-core(at)postgresql(dot)org>, Andres Freund <andres(at)anarazel(dot)de> |
Subject: | Re: [CORE] back-branch multixact fixes & 9.5 alpha/beta: schedule |
Date: | 2015-06-09 12:01:59 |
Message-ID: | CA+Tgmobnq=RJoN2h4RKU4OgRN9ONRwz=-e1T5d=-9ZvEutoSmg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Jun 9, 2015 at 3:04 AM, David Gould <daveg(at)sonic(dot)net> wrote:
> On Mon, 8 Jun 2015 13:53:42 -0300
> Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> wrote:
>
>> * people with the wrong oldestMulti setting in pg_control (which would
>> be due to a buggy pg_upgrade being used long ago) will be unable to
>> start if they upgrade to 9.3.7 or 9.3.8. A solution for them would be
>> to downgrade to 9.3.6. We had reports of this problem starting just a
>> couple of days after we released 9.4.2, I think.
>
> Does this mean that for people with wrong oldestMulti settings in pg_control
> due to a buggy pg_upgrade being used long ago can fix this by updating to
> 9.3.9 when it is released? Asking for a friend...
If the value is buggy because it is 1 when it should have some larger
value, yes, this should fix it.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Jeevan Chalke | 2015-06-09 12:29:52 | Re: psql :: support for \ev viewname and \sv viewname |
Previous Message | Jeevan Chalke | 2015-06-09 11:54:28 | Re: bugfix: incomplete implementation of errhidecontext |