pg_upgrade broken by xlog numbering - Mailing list pgsql-hackers

From Kevin Grittner
Subject pg_upgrade broken by xlog numbering
Date
Msg-id 4FE80F320200002500048A6C@gw.wicourts.gov
Whole thread Raw
Responses Re: pg_upgrade broken by xlog numbering
Re: pg_upgrade broken by xlog numbering
Re: pg_upgrade broken by xlog numbering
List pgsql-hackers
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




pgsql-hackers by date:

Previous
From: Ryan Kelly
Date:
Subject: Re: [PATCH] Allow breaking out of hung connection attempts
Next
From: Magnus Hagander
Date:
Subject: Re: libpq compression