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

Re: WAL does not recover gracefully from out-of-disk-space

From: Vadim Mikheev <vadim4o(at)email(dot)com>
To: Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: WAL does not recover gracefully from out-of-disk-space
Date: 2001-02-26 15:50:08
Message-ID: 383179699.983202608508.JavaMail.root@web446-ec.mail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
>> Regardless of whether this particular behavior is fixable,
>> this brings up something that I think we *must* do before
>> 7.1 release: create a utility that blows away a corrupted
>> logfile to allow the system to restart with whatever is in
>> the datafiles.  Otherwise, there is no recovery technique
>> for WAL restart failures, short of initdb and restore from
>> last backup.  I'd rather be able to get at data of
>> questionable up-to-dateness than not have any chance of
>> recovery at all.
>
> I've asked 2 or 3 times how to recover from recovery failure
> but got no answer. We should some recipi for the failure
> before 7.1 release.

And I answered 2 or 3 times with fixes for each reported
recovery failure -:) (And asked to help with testing...)

Seems to me that "fixing" is the only "answer" you would
get asking the same question to Oracle, Informix or any
other system with transaction log. Does anybody know how
"big boys" deal with this issue?

Vadim

-----------------------------------------------
FREE! The World's Best Email Address @email.com
Reserve your name now at http://www.email.com



pgsql-hackers by date

Next:From: Zeugswetter Andreas SBDate: 2001-02-26 15:51:33
Subject: AW: AW: WAL does not recover gracefully from out-of-disk-sp ace
Previous:From: Tom LaneDate: 2001-02-26 15:39:56
Subject: Re: AW: WAL does not recover gracefully from out-of-disk-sp ace

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