From: Christoph Haller <ch@rodos.fzk.de>
To: richard@ibisaustralia.com
Cc: pgsql-sql@postgresql.org
Subject: Re: Ooops ! :( Recovery techniques
Date: Tue, 02 Dec 2003 16:25:51 MET
Message-ID: <200312021525.QAA18638@rodos> (raw)
In-Reply-To: <017b01c3b7c5$7328cd40$61c58690@athlon2000>
>
> My machine just crashed in the middle of an update.
>
> When I restart the postgresql server the database engine appears ok and the=
> n tells me that a file /data/pg_clog/0697 is not there.=20
>
> I presume that these are the transaction log files.=20
> I would like to truncate the old logfiles, re-index and keep going.
> I that possible with postgres of do I have to do a full rebuild?
>
> thanks verymuch
>
> Richard Sydney-Smith
>
>
Sorry, your presumption is wrong. In contrary to what the name might
suggest this file is not a log file at all.
Your dbase is probably seriously damaged.
If you haven't made a dbase dump using "pg_dump" before,
you'd better do that full rebuild you mentioned.
Regards, Christoph
PS I recommend to read the chapter 'Backup and Restore' of the
fine manual to be prepared when your machine crashes again.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: ch@rodos.fzk.de, richard@ibisaustralia.com
Subject: Re: Ooops ! :( Recovery techniques
In-Reply-To: <200312021525.QAA18638@rodos>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox