Re: could not write block & xlog flush request 3FD/0 is not satisfied

From: Yves Weißig <weissig(at)rbg(dot)informatik(dot)tu-darmstadt(dot)de>
To: "'Greg Stark'" <gsstark(at)mit(dot)edu>
Cc: <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: could not write block & xlog flush request 3FD/0 is not satisfied
Date: 2011-05-09 10:09:04
Message-ID: 006301cc0e31$23601eb0$6a205c10$@rbg.informatik.tu-darmstadt.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

All right, what would we be the best way to debug such a problem?

Yves

-----Original Message-----
From: pgsql-hackers-owner(at)postgresql(dot)org
[mailto:pgsql-hackers-owner(at)postgresql(dot)org] On Behalf Of Greg Stark
Sent: Sunday, May 08, 2011 6:36 PM
To: weissig(at)rbg(dot)informatik(dot)tu-darmstadt(dot)de
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: [HACKERS] could not write block & xlog flush request 3FD/0 is
not satisfied

On Sun, May 8, 2011 at 4:18 PM, Yves Weißig
<weissig(at)rbg(dot)informatik(dot)tu-darmstadt(dot)de> wrote:
> ERROR:  xlog flush request 3FD/0 is not satisfied --- flushed only to
> 0/20E2DC4
>

That's a pretty big difference in log positions. It seems likely you've
overwritten the block header writing garbage to the LSN.

--
greg

--
Sent via pgsql-hackers mailing list (pgsql-hackers(at)postgresql(dot)org) To make
changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Heikki Linnakangas 2011-05-09 10:19:23 Re: Process wakeups when idle and power consumption
Previous Message Peter Geoghegan 2011-05-09 09:20:05 Re: Process wakeups when idle and power consumption