
> > > #2  0x20dc71 in abort () from /lib/libc.so.6
> > > #3  0x8080495 in XLogFileOpen ()
> > 
> > Hm.  Evidently it's failing to open the xlog file, but the code is set
> > up in such a way that it dies before telling you why :-( Take a look
> > at XLogFileOpen in src/backend/access/transam/xlog.c and tweak the code
> > to tell you the path and errno it's failing on before it abort()s.
> 
> I don't remember why there is abort() in XLogFileOpen just before
> appropriate elog(STOP) there - I'll remove it in few moments, - but
> it's already obvious why open failed: there is no file with checkpoint
> record pointed by pg_control - data/pg_xlog/000000000000002F.
> So, the question is who removed this file - PG or Linux?

Might it be, that pg_control is older than it should be ?
I mean, that the write to pg_control did not make it to disk,
but the checkpoint already completed (removed the logs) ?

Andreas

Tue, 13 Feb 2001 10:26:38 +0100
Zeugswetter Andreas SB  <ZeugswetterA@wien.spardat.at>
AW: Recovery of PGSQL after system crash failing!!! 