From: | Vipul(dot)Gupta(at)trilogy(dot)com |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: xlog flush request error |
Date: | 2005-11-25 04:48:17 |
Message-ID: | OF216BE6EA.7FF65954-ON862570C4.001A3FC6@trilogy.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
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(at)sss(dot)pgh(dot)pa(dot)us>
11/24/2005 09:07 PM
To: Vipul(dot)Gupta(at)trilogy(dot)com
cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: [PERFORM] xlog flush request error
Vipul(dot)Gupta(at)trilogy(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2005-11-25 04:59:26 | Re: xlog flush request error |
Previous Message | Kyle Cordes | 2005-11-25 03:15:44 | Re: 8.1 count(*) distinct: IndexScan/SeqScan |