problems after server crash - Mailing list pgsql-bugs

From Martin Würtele
Subject problems after server crash
Date
Msg-id 20011025175349.A22729@independence.wuertele.net
Whole thread Raw
List pgsql-bugs
hi,

1. unfortunately i can't subscribe to the mailinglist - it doesn't send me
the confirmation mail so please cc me.

2. 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:

Previous
From: Bill Studenmund
Date:
Subject: Re: Enabling --debug causes regression test failure.
Next
From: pgsql-bugs@postgresql.org
Date:
Subject: Bug #493: corrupt pg_language_oid_index, (how to fix?)