Re: unexpected pageaddr error in db log

From: wd <wd(at)wdicc(dot)com>
To: bricklen <bricklen(at)gmail(dot)com>
Cc: Amit Langote <amitlangote09(at)gmail(dot)com>, PostgreSQL General <pgsql-general(at)postgresql(dot)org>
Subject: Re: unexpected pageaddr error in db log
Date: 2013-12-21 02:35:20
Message-ID: CABexzmhUP5H2XY14=sWT4SpCOn-mBWcmtQgz6EJpeO3FoE=a2A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Thu, Dec 19, 2013 at 11:56 PM, bricklen <bricklen(at)gmail(dot)com> wrote:

>
> On Thu, Dec 19, 2013 at 1:27 AM, wd <wd(at)wdicc(dot)com> wrote:
>
>>
>> On Thu, Dec 19, 2013 at 2:24 PM, Amit Langote <amitlangote09(at)gmail(dot)com>wrote:
>>
>>> "unexpected pageaddr" log entry in this case means the standby reached
>>> the end of existing WAL.
>>> So, just before connecting to walsender for streaming replication, it
>>> logs this.
>>>
>>
>>
>> Thanks for your reply. So this means I can safely omit this message?
>>
>
> Yes, you can ignore that message. It message level was something more
> severe than "[LOG]" then it would be worth investigating further.
>
>
Ok,thanks. :)

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Gavin Flower 2013-12-21 02:42:28 Re: to_json(now()) result doesn't have 'T' separator
Previous Message Joe Van Dyk 2013-12-21 02:27:45 Re: to_json(now()) result doesn't have 'T' separator