Alvaro Herrera wrote: Heikki, Andres,
> Shortly after this patch was committed, buildfarm member locust (running > Mac OS X 10.5 apparently) started failing the pg_upgrade check: > > command: > "/Users/pgbuildfarm/Documents/workdir/HEAD/pgsql.82393/contrib/pg_upgrade/tmp_check/install//Users/pgbuildfarm/Documents/workdir//HEAD/inst/bin/pg_ctl" > -w -l "pg_upgrade_server.log" -D > "/Users/pgbuildfarm/Documents/workdir/HEAD/pgsql.82393/contrib/pg_upgrade/tmp_check/data" > -o "-p 57632 -b -c synchronous_commit=off -c fsync=off -c > full_page_writes=off -c listen_addresses='' -c unix_socket_permissions=0700 > -c > unix_socket_directories='/Users/pgbuildfarm/Documents/workdir/HEAD/pgsql.82393/contrib/pg_upgrade'" > start >> "pg_upgrade_server.log" 2>&1 > waiting for server to start....LOG: database system was shut down at > 2013-12-19 12:51:16 CET > LOG: invalid primary checkpoint record > LOG: invalid secondary checkpoint link in control file > PANIC: could not locate a valid checkpoint record Any comment on this problem? Somehow ReadRecord is unable to find a checkpoint, yet there's no error message to be seen anywhere, whereas pg_resetxlog does report it: > command: > "/Users/pgbuildfarm/Documents/workdir/HEAD/pgsql.82393/contrib/pg_upgrade/tmp_check/install//Users/pgbuildfarm/Documents/workdir//HEAD/inst/bin/pg_resetxlog" > -l 000000010000000000000009 > "/Users/pgbuildfarm/Documents/workdir/HEAD/pgsql.82393/contrib/pg_upgrade/tmp_check/data" > >> "pg_upgrade_utility.log" 2>&1 > pg_resetxlog: could not read from directory "pg_xlog": Invalid argument I cannot but think xlogreader is at fault. Regardless of the solution to the Mac OS X problem, ISTM this should be fixed. -- Álvaro Herrera http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
