Re: Problem with pg_upgrade 8.3 to 9.1.4 - clog missing?!

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: hubert depesz lubaczewski <depesz(at)depesz(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Problem with pg_upgrade 8.3 to 9.1.4 - clog missing?!
Date: 2012-06-13 18:55:41
Message-ID: 20120613185541.GE4418@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Wed, Jun 13, 2012 at 08:43:23PM +0200, hubert depesz lubaczewski wrote:
> On Wed, Jun 13, 2012 at 02:32:21PM -0400, Bruce Momjian wrote:
> > I assume 8.3 vacuumdb did not generate these errors. If it was 8.4 I
> > would suggest it was because we don't copy visibility map files from
> > pre-9.1 because those were not crash-safe, but 8.3 didn't have
> > visibility map files (added in PG 8.4), so 8.3 should have been checking
> > the exact same transaction ids as 9.1.
> >
> > Basically, I can't think of a cause.
>
> yeah, neither can we. but - any other test - even using the same source
> of $PGDATA went flawless. I'm tempted to assume it's just a random
> glitch in matrix, and just go on.

Is the vacuumdb still repeatedly failing?

--
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

Responses

Browse pgsql-general by date

  From Date Subject
Next Message hubert depesz lubaczewski 2012-06-13 19:24:20 Re: Problem with pg_upgrade 8.3 to 9.1.4 - clog missing?!
Previous Message hubert depesz lubaczewski 2012-06-13 18:43:23 Re: Problem with pg_upgrade 8.3 to 9.1.4 - clog missing?!