Postgres Pro
Downloads
Home   >   mailing lists

Re: xlog flush request error - Mailing list pgsql-performance

From Vipul.Gupta@trilogy.com
Subject Re: xlog flush request error
Date
Msg-id OF216BE6EA.7FF65954-ON862570C4.001A3FC6@trilogy.com
Whole thread Raw
In response to xlog flush request error  (Vipul.Gupta@trilogy.com)
Responses Re: xlog flush request error
List pgsql-performance
Tree view

Hi tom,

basically when i run any query with database say,

select count(*) from table1;

It gives me the following error trace:
WARNING:  could not write block 297776 of 1663/2110743/2110807
DETAIL:  Multiple failures --- write error may be permanent.
ERROR:  xlog flush request 7/7D02338C is not satisfied --- flushed only to 3/2471E324
 writing block 297776 of relation 1663/2110743/2110807
xlog flush request 7/7D02338C is not satisfied --- flushed only to 3/2471E324
xlog flush request 7/7D02338C is not satisfied --- flushed only to 3/2471E324\q

i tried using pg_resetxlog but till date, have not been able to solve this problem

Regards,
Vipul Gupta



Tom Lane <tgl@sss.pgh.pa.us>

11/24/2005 09:07 PM

       
        To:        Vipul.Gupta@trilogy.com
        cc:        pgsql-performance@postgresql.org
        Subject:        Re: [PERFORM] xlog flush request error



Vipul.Gupta@trilogy.com writes:
> Can anyone suggest how do i fix this

>  xlog flush request 7/7D02338C is not satisfied --- flushed only to
> 3/2471E324

This looks like corrupt data to me --- specifically, garbage in the LSN
field of a page header.  Is that all you get?  PG 7.4 and up should tell
you the problem page number in a CONTEXT: line.

                                                  regards, tom lane



pgsql-performance by date:

Previous
From: Kyle Cordes
Date:
Subject: Re: 8.1 count(*) distinct: IndexScan/SeqScan
Next
From: Tom Lane
Date:
Subject: Re: xlog flush request error