On Sun, Dec 29, 2013 at 02:48:21AM -0500, Tom Lane wrote: > There are three or four different bugs here, but the key points are: > > 1. pg_resetxlog is diligently trashing every single WAL file in pg_xlog/, > and then failing (by virtue of some ancient OS X bug in readdir()), so > that it doesn't get to the point of recreating a WAL file with a > checkpoint record. > > 2. pg_resetxlog already rewrote pg_control, which might not be such a hot > idea; but whether it had or not, pg_control's last-checkpoint pointer > would be pointing to a WAL file that is not in pg_xlog/ now. > > 3. pg_upgrade ignores the fact that pg_resetxlog failed, and keeps going.
Does pg_resetxlog return a non-zero exit status? If so, pg_upgrade should have caught that and exited. -- Bruce Momjian <br...@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + Everyone has their own god. + -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
