Re: Invalid headers and xlog flush failures

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bricklen Anderson <BAnderson(at)PresiNET(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Invalid headers and xlog flush failures
Date: 2005-02-02 17:09:30
Message-ID: 29755.1107364170@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Bricklen Anderson <BAnderson(at)PresiNET(dot)com> writes:
> Feb 1 11:17:50 dev94 postgres[4959]: [472-1] 2005-02-01 11:17:50 PST> ERROR: xlog flush request
> 972/FC932854 is not satisfied --- flushed only to 73/86D2640

Hmm, have you perhaps played any games with pg_resetxlog in this database?

I would have suggested that maybe this represented on-disk data
corruption, but the appearance of two different but not-too-far-apart
WAL offsets in two different pages suggests that indeed the end of WAL
was up around segment 972 or 973 at one time. And now it's evidently
ending at 73. Not good. What file names do you see in pg_xlog/, and
what does pg_controldata show?

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Lonni J Friedman 2005-02-02 17:10:59 Re: capturing/viewing sort_mem utilization on a per query basis
Previous Message Scott Marlowe 2005-02-02 17:07:15 Re: basic pg lock question