From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Andrew Sullivan <ajs(at)crankycanuck(dot)ca> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Strange error while executing query from front end: |
Date: | 2006-01-17 15:30:59 |
Message-ID: | 28570.1137511859@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Andrew Sullivan <ajs(at)crankycanuck(dot)ca> writes:
> On Mon, Jan 16, 2006 at 09:27:30AM +0530, Mavinakuli, Prasanna (STSD) wrote:
>> ERROR: xlog flush request 0/108EA5F8 is not satisfied --- flushed only
>> to 0/1813C60
> If I had to guess, I'd say you're having a hard disk failure of some
> kind. In particular, this tells you that a flush of the write ahead
> log isn't completing. That's a Bad Thing.
Actually it looks like corrupt data to me: some page's LSN field
contains a value that is past the actual end of WAL, and therefore
isn't a correct copy of the location of the last WAL record affecting
that page, as it's supposed to be.
Could have resulted from a hardware error, but it's hard to tell.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Bogdoll, Dieter | 2006-01-17 15:33:46 | auto increment within a compound key |
Previous Message | Tom Lane | 2006-01-17 15:27:31 | Re: Huge number of disk writes after migration to 8.1 |