| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | Jesse Denardo <denaje(at)gmail(dot)com>, pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: 9.3beta2: Failure to pg_upgrade |
| Date: | 2013-07-31 17:06:31 |
| Message-ID: | 20130731170631.GG3716@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
On Wed, Jul 31, 2013 at 12:56:33PM -0400, Alvaro Herrera wrote:
> Bruce Momjian escribió:
> > On Tue, Jul 30, 2013 at 10:17:52AM -0400, Jesse Denardo wrote:
>
> > So, first, this is new in 9.3, and second, it seems the comment "we need
> > to reset pg_control so that the new server doesn't attempt to read
> > multis older than the cutoff value" is not working. Alvaro, can you
> > comment on this? I think you added this code with this commit:
>
> So it seems. I will have a look.
Well, the good news is that this is new 9.3 code, this bug was caught
during beta, and pg_upgrade failed visibly, rather than silently.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jesse Denardo | 2013-07-31 17:18:31 | Re: 9.3beta2: Failure to pg_upgrade |
| Previous Message | Alvaro Herrera | 2013-07-31 16:56:33 | Re: 9.3beta2: Failure to pg_upgrade |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ivan Lezhnjov IV | 2013-07-31 17:08:12 | backup.sgml-cmd-v003.patch |
| Previous Message | Alvaro Herrera | 2013-07-31 16:56:33 | Re: 9.3beta2: Failure to pg_upgrade |