AW: Recovery of PGSQL after system crash failing!!!

From: Zeugswetter Andreas SB <ZeugswetterA(at)wien(dot)spardat(dot)at>
To: "'Vadim Mikheev'" <vmikheev(at)sectorbase(dot)com>, Ryan Kirkpatrick <pgsql(at)rkirkpat(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: AW: Recovery of PGSQL after system crash failing!!!
Date: 2001-02-13 09:26:38
Message-ID: 11C1E6749A55D411A9670001FA6879633681F3@sdexcsrv1.f000.d0188.sd.spardat.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


> > > #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

Browse pgsql-hackers by date

  From Date Subject
Next Message Hannu Krosing 2001-02-13 12:05:35 Re: locale support
Previous Message Vadim Mikheev 2001-02-13 08:18:59 Re: Recovery of PGSQL after system crash failing!!!