Re: WAL Streaming Failure PostgreSQL 9.4

From: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>
To: Ivann Ruiz <ivann(dot)jprog(at)gmail(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: WAL Streaming Failure PostgreSQL 9.4
Date: 2015-05-28 17:21:25
Message-ID: CAMkU=1zxTqO2u0GcLm8SThq4CiVhsHV_V_pJWTT-AbjpDE7xJw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On May 28, 2015 9:58 AM, "Ivann Ruiz" <ivann(dot)jprog(at)gmail(dot)com> wrote:

> When I execute pg_ctl start on my standby I get the following
>
> LOG: database system was interrupted; last known up at 2015-05-27
14:16:41 EDT
> LOG: entering standby mode
> LOG: restored log file "000000010000000000000028" from archive
> LOG: redo starts at 0/28000090
> LOG: consistent recovery state reached at 0/280000B8
> LOG: unexpected pageaddr 0/24000000 in log segment
000000010000000000000029, offset 0
> LOG: started streaming WAL from primary at 0/29000000 on timeline 1
>
> And on my master I have
>
> LOG: database system was shut down at 2015-05-27 16:00:14 EDT
> LOG: database system is ready to accept connections
> LOG: autovacuum launcher started
>
> And then nothing else happens, please I really need help with this, I
appreciate all comments. Any questions, please feel free to ask.

Are you applying any load to master? If not, nothing needs to be
replicated so there is nothing to happen. If this is just for testing, run
pgbench -T 3600.

Cheers, Jeff

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2015-05-28 17:24:24 Re: Partitioning and performance
Previous Message Tom Lane 2015-05-28 17:13:10 Re: Partitioning and performance