Re: Error in Postgresql after a Machine Crash

From: "Qingqing Zhou" <zhouqq(at)cs(dot)toronto(dot)edu>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: Error in Postgresql after a Machine Crash
Date: 2006-03-15 08:24:16
Message-ID: dv8j5q$9fs$1@news.hub.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general


""Paulo Henrique Oliveira"" <baptista(at)gmail(dot)com> wrote
> I was using postgres 7.2.1 in a Debian Woody server (in prodution).
> The machine crashed and when I restart it the following error occurs a lot
> in log.
> 2006-03-14 14:35:23 [11858] ERROR: XLogFlush: request 102/7407C864 is
not
> satisfied --- flushed only to 102/4CFEC030
>
This happens due to a broken LSN field on the page header. Now seems that
number is quite insane, which is much much bigger than the actual current of
WAL. If there is a lot of different complains like this (compare the
7407C864 field), then there are a lot of broken pages :-(

> How do I fix this?
Are you sure you are using 7.2.1? Now PG don't support version older than
7.3 officially. So the best way is upgrade to a newer vesion like 7.4. You
can dump your data before that.

Regards,
Qingqing

In response to

Browse pgsql-general by date

  From Date Subject
Next Message surabhi.ahuja 2006-03-15 08:55:40 Re: out of memory
Previous Message chris smith 2006-03-15 07:13:09 Re: out of memory using Postgres with Spring/Hibernate/Java