Re: warning message in standby

From: Simon Riggs <simon(at)2ndQuadrant(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: warning message in standby
Date: 2010-06-11 12:19:39
Message-ID: 1276258779.23257.16585.camel@ebony
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, 2010-06-10 at 09:57 -0400, Robert Haas wrote:
> On Mon, Jun 7, 2010 at 9:21 AM, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
> wrote:
> > When an error is found in the WAL streamed from the master, a
> warning
> > message is repeated without interval forever in the standby. This
> > consumes CPU load very much, and would interfere with read-only
> queries.
> > To fix this problem, we should add a sleep into
> emode_for_corrupt_record()
> > or somewhere? Or we should stop walreceiver and retry to read WAL
> from
> > pg_xlog or the archive?
>
> I ran into this problem at one point, too, but was in the middle of
> trying to investigate a different bug and didn't have time to track
> down what was causing it.

So you saw a bug, but didn't report it? Why was that?

I find it amazing that such an obvious problem wasn't covered in
testing, nor do we have a clear plan in the design for handling it.

How many other things are known about but not reported?

If anybody has bugs, report them now.

--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Training and Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Devrim GÜNDÜZ 2010-06-11 12:25:24 Re: PG 9.1 tentative timeline
Previous Message Stephen Frost 2010-06-11 12:15:20 Re: PG 9.1 tentative timeline