Re: pg_upgrade broken by xlog numbering - Mailing list pgsql-hackers

From Thom Brown
Subject Re: pg_upgrade broken by xlog numbering
Date
Msg-id CAA-aLv6SEU3=hM0pGFFhFJV6e-NLMzGy8DDttauuVSiYm58H1w@mail.gmail.com
Whole thread Raw
In response to pg_upgrade broken by xlog numbering  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
List pgsql-hackers
On 25 June 2012 13:11, Kevin Grittner <Kevin.Grittner@wicourts.gov> wrote:
> On HEAD at the moment, `make check-world` is failing on a 32-bit Linux
> build:
>
> + pg_upgrade -d
> /home/kevin/pg/master/contrib/pg_upgrade/tmp_check/data.old -D
> /home/kevin/pg/master/contrib/pg_upgrade/tmp_check/data -b
> /home/kevin/pg/master/contrib/pg_upgrade/tmp_check/install//home/kevin/pg/master/Debug/bin
> -B
> /home/kevin/pg/master/contrib/pg_upgrade/tmp_check/install//home/kevin/pg/master/Debug/bin
> Performing Consistency Checks
> -----------------------------
> Checking current, bin, and data directories                 ok
> Checking cluster versions                                   ok
> Some required control information is missing;  cannot find:
>  first log file ID after reset
>  first log file segment after reset
>
> Cannot continue without required control information, terminating
> Failure, exiting

I get precisely the same on 64-bit Linux.

--
Thom


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [PATCH 04/16] Add embedded list interface (header only)
Next
From: "David E. Wheeler"
Date:
Subject: Re: warning handling in Perl scripts