On Thu, Dec 19, 2013 at 11:56 PM, bricklen wrote:
>
> On Thu, Dec 19, 2013 at 1:27 AM, wd wrote:
>
>>
>> On Thu, Dec 19, 2013 at 2:24 PM, Amit Langote wrote:
>>
>>> "unexpected pageaddr" log entry in this case means the standby reached
>>> the end of existing WAL.
>>> So, just before connecting
On Thu, Dec 19, 2013 at 1:27 AM, wd wrote:
>
> On Thu, Dec 19, 2013 at 2:24 PM, Amit Langote 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.
>>
>
>
On Thu, Dec 19, 2013 at 2:24 PM, Amit Langote 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 t
On Thu, Dec 19, 2013 at 12:25 PM, wd wrote:
>
> hi,
>
> We have upgrade our database from PostgreSQL 9.2.4 to 9.3.2, use dump &
> restore in a fresh db created by initdb.
>
> Then use pg_basebackup created 2 slave db, the error occur when start the
> database.
>
> db1
>
> [2013-12-19 04:00:5
