9.0devel (cvs yesterday) primary+server, with this patch:
extend_format_of_recovery_info_funcs_v2.patch
( http://archives.postgresql.org/pgsql-hackers/2010-02/msg02116.php )
A large (500 GB) restore left to run overnight, gave the below crash. The
standby was restarted,
and seems to be catching up OK.
LOG: entering standby mode
LOG: redo starts at 0/1000020
LOG: consistent recovery state reached at 0/2000000
LOG: database system is ready to accept read only connections
TRAP: FailedAssertion("!(((xid) != ((TransactionId) 0)))", File: "twophase.c",
Line: 1201)
LOG: startup process (PID 21044) was terminated by signal 6: Aborted
LOG: terminating any other active server processes
LOG: database system was interrupted while in recovery at log time 2010-02-26
06:42:14 CET
HINT: If this has occurred more than once some data might be corrupted and you
might need to
choose an earlier recovery target.
cp: cannot stat
`/var/data1/pg_stuff/dump/hotslave/replication_archive/00000001000000150000003F':
No such file or directory
LOG: entering standby mode
LOG: redo starts at 15/3400E828
LOG: consistent recovery state reached at 15/6D6D9FD8
LOG: database system is ready to accept read only connections
(btw, I think I have seen this exact same one (File "twophase.c", Line: 1201) a
few times before,
without reporting it here, so it might have no connection to this particular
patch. Sorry to be
vague about that)
Is it useful to report these cases of FailedAssertion?
Erik Rijkers
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
