Re: xlog loose ends, continued - Mailing list pgsql-hackers

From Tom Lane
Subject Re: xlog loose ends, continued
Date
Msg-id 20455.984507614@sss.pgh.pa.us
Whole thread Raw
In response to RE: xlog loose ends, continued  ("Mikheev, Vadim" <vmikheev@SECTORBASE.COM>)
List pgsql-hackers
"Mikheev, Vadim" <vmikheev@SECTORBASE.COM> writes:
>> What I was thinking about in that last paragraph was manual 
>> analysis and recovery. I don't think it's a good idea for automatic
>> system startup to skip over gaps in the log.

> But if we'll not try to read after gap then after restart system will
> not notice gap and valid records after it and just rewrite log space
> with new records. Not much chance for manual analysis - ppl will
> not report any problems.

That'll be true in any case, unless we refuse to start up at all upon
detecting xlog corruption (which doesn't seem like the way to fly).
Not sure what we can do about that.
        regards, tom lane


pgsql-hackers by date:

Previous
From: "Mikheev, Vadim"
Date:
Subject: RE: xlog loose ends, continued
Next
From: "Mikheev, Vadim"
Date:
Subject: RE: Another little xlog change idea