Re: pg_upgrade broken by xlog numbering

On Mon, Jun 25, 2012 at 8:11 AM, 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

On MacOS X, on latest sources, initdb fails:

creating directory /Users/rhaas/pgsql/src/test/regress/./tmp_check/data ... ok
creating subdirectories ... ok
selecting default max_connections ... 100
selecting default shared_buffers ... 32MB
creating configuration files ... ok
creating template1 database in
/Users/rhaas/pgsql/src/test/regress/./tmp_check/data/base/1 ... ok
initializing pg_authid ... ok
initializing dependencies ... ok
creating system views ... ok
loading system objects' descriptions ... ok
creating collations ... ok
creating conversions ... ok
creating dictionaries ... FATAL:  control file contains invalid data
child process exited with exit code 1
initdb: data directory
"/Users/rhaas/pgsql/src/test/regress/./tmp_check/data" not removed at
user's request

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company