Skip site navigation (1) Skip section navigation (2)

postgres crash

From: Martin Würtele <martin(at)wuertele(dot)net>
To: pgsql-bugs(at)postgresql(dot)org
Subject: postgres crash
Date: 2001-10-25 15:51:57
Message-ID: 20011025175157.A22636@independence.wuertele.net (view raw or flat)
Thread:
Lists: pgsql-bugs
hi,

we had a server crash today - had to fsck and postgres is corrupted now

if i try a pg_dump i get:

inetmain:/tmp/tests$ pg_dump -c -v -d factline1 > /tmp/factline1_20011025_144800.sql
--  saving database definition
getDatabase(): SELECT failed.  Explanation from backend: 'ERROR:  pg_atoi:
error in "t": can't parse "t"
'.

i get the same error if i try to dump a table.

i deleted all indexes as there were lot's of problems with them but this
didn't help ether.

i changed src/backend/access/transam/xlog.c
from 

if (XLByteLT(LogwrtResult.Flush, record))
  elog(STOP, "XLogFlush: request is not satisfied");
break;

to

if (XLByteLT(LogwrtResult.Flush, record))
  elog(DEBUG, "XLogFlush: request (%u, %u) is not satisfied --- flushed to (%u, %u)",
  record.xlogid, record.xrecoff,
  LogwrtResult.Flush.xlogid, LogwrtResult.Flush.xrecoff);
break;

because otherwise postgres wouldn't even start.

my question: how can i either get a dump of my data or a running database
back. i did a backup of /var/lib/postgresql/data before removing indexes so
i still have the version after the crash.

tia martin
-- 
factline Krisper Fabro Harnoncourt OEG (www.factline.com)

pgsql-bugs by date

Next:From: Martin WürteleDate: 2001-10-25 15:53:49
Subject: problems after server crash
Previous:From: Tom LaneDate: 2001-10-25 14:12:14
Subject: Re: Enabling --debug causes regression test failure.

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group