Re: [GENERAL] pg_upgrade problem

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: depesz(at)depesz(dot)com
Cc: PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org>
Subject: Re: [GENERAL] pg_upgrade problem
Date: 2011-08-31 17:24:05
Message-ID: 201108311724.p7VHO5F16882@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

hubert depesz lubaczewski wrote:
> On Wed, Aug 31, 2011 at 12:16:03PM -0400, Bruce Momjian wrote:
> > hubert depesz lubaczewski wrote:
> > > On Fri, Aug 26, 2011 at 12:18:55AM -0400, Bruce Momjian wrote:
> > > >
> > > > OK, this was very helpful. I found out that there is a bug in current
> > > > 9.0.X, 9.1.X, and HEAD that I introduced recently when I excluded temp
> > > > tables. (The bug is not in any released version of pg_upgrade.) The
> > > > attached, applied patches should fix it for you. I assume you are
> > > > running 9.0.X, and not 9.0.4.
> > >
> > > pg_upgrade worked. Now I'm doing reindex and later on vacuumdb -az.
> > >
> > > will keep you posted.
> >
> > FYI, this pg_upgrade bug exists in PG 9.1RC1, but not in earlier betas.
> > Users can either wait for 9.1 RC2 or Final, or use the patch I posted.
> > The bug is not in 9.0.4 and will not be in 9.0.5.
>
> I assume you mean the bug that caused pg_upgrade to fail.

Yes.

> But there still is (existing in 9.0.4 too) bug which causes vacuum to
> fail.

Yes. We need to find the cause of that new bug.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ It's impossible for everything to be true. +

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2011-08-31 17:24:21 Re: "invalid input syntax for type bytea"
Previous Message Bruce Momjian 2011-08-31 17:23:05 Re: [GENERAL] pg_upgrade problem

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2011-08-31 17:31:07 Re: [GENERAL] pg_upgrade problem
Previous Message Bruce Momjian 2011-08-31 17:23:05 Re: [GENERAL] pg_upgrade problem