Re: xlog loose ends, continued

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Mikheev, Vadim" <vmikheev(at)SECTORBASE(dot)COM>
Cc: pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: xlog loose ends, continued
Date: 2001-03-13 18:20:14
Message-ID: 20455.984507614@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"Mikheev, Vadim" <vmikheev(at)SECTORBASE(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Mikheev, Vadim 2001-03-13 18:25:41 RE: Another little xlog change idea
Previous Message Mikheev, Vadim 2001-03-13 18:15:02 RE: xlog loose ends, continued