Re: warning message in standby

On Fri, Jun 11, 2010 at 8:19 AM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
> 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?

Because it happened while I was in the middle of trying to investigate
a different bug, and I didn't know precisely what I had done to cause
it. I could have reported it anyway, but I thought it would not have
been that helpful to report a bug that I didn't know for sure how to
reproduce. Like everyone else here, I am working very hard and do not
always have time to follow up on every issue. I had something else
weird happen yesterday but I'm not sure I know exactly what I did and
I'm not at all sure that it wasn't just pilot error. If I start
reporting every pilot error as a bug, I'm going to get laughed out of
town, because I make a pilot error *every time* I tried to set up SR
w/HS. :-(

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company