Re: warm standby resume and take online problems - Mailing list pgsql-general

From Greg Smith
Subject Re: warm standby resume and take online problems
Date
Msg-id alpine.GSO.2.01.0911042039120.15465@westnet.com
Whole thread Raw
In response to warm standby resume and take online problems  (Michal Bicz <michal.bicz@iloopmobile.com>)
Responses Re: warm standby resume and take online problems
List pgsql-general
On Wed, 4 Nov 2009, Michal Bicz wrote:

> Now it is saying constantly in log :
> 2009-11-04 04:57:39 PST : ERROR:  XX000: xlog flush request 2FB/28CE63A8 is not satisfied --- flushed only to
2FB/8FFEA60
> 2009-11-04 04:57:39 PST : CONTEXT:  writing block 874937 of relation 1663/20863/21548
> 2009-11-04 04:57:39 PST : LOCATION:  XLogFlush, xlog.c:1865
> 2009-11-04 04:57:39 PST : WARNING:  58030: could not write block 874937 of 1663/20863/21548
> 2009-11-04 04:57:39 PST : DETAIL:  Multiple failures --- write error may be permanent.
> 2009-11-04 04:57:39 PST : LOCATION:  AbortBufferIO, bufmgr.c:2129

I think you can run into this if disk space on the xlog drive fills up,
which is easy to do with complicated WAL shipping setups if you're not
careful.  You might want to double-check that, and check for general disk
I/O errors too.  A write error at this point is kind of odd even if you
abused recovery a bit leading up to here.  This might be a full disk or a
bad block on the xlog drive instead of something more complicated.

--
* Greg Smith gsmith@gregsmith.com http://www.gregsmith.com Baltimore, MD

pgsql-general by date:

Previous
From: "Ow Mun Heng"
Date:
Subject: Re: --//pgsql partitioning-///--------------------
Next
From: Tom Lane
Date:
Subject: Re: error caused by FOREIGN KEY on composite type