Re: Turning slave into a master - PostgreSQL 9.2 - Mailing list pgsql-general

From Patrick B
Subject Re: Turning slave into a master - PostgreSQL 9.2
Date
Msg-id CAJNY3itEJpmkHf1si14x4gTTV-9NPGo3G=nUcZmD0Nm_5EzUxA@mail.gmail.com
Whole thread Raw
In response to Re: Turning slave into a master - PostgreSQL 9.2  (Patrick B <patrickbakerbr@gmail.com>)
List pgsql-general


2016-11-02 8:43 GMT+13:00 Patrick B <patrickbakerbr@gmail.com>:


2016-11-02 2:55 GMT+13:00 Scott Marlowe <scott.marlowe@gmail.com>:
On Mon, Oct 31, 2016 at 8:01 PM, Patrick B <patrickbakerbr@gmail.com> wrote:
> If I change recovery.conf:
>
> recovery_target_time = '2016-10-30 02:24:40'
>
>
> I get error:
>
> FATAL:  requested recovery stop point is before consistent recovery point

You can try using pg_basebackup to get the replica setup. In 9.2 you
gotta make your own recovery.conf, but you already know how to do
that. Way easier than trying to rsync by hand etc.


I did a pg_basebackup!


Hi guys,

I was able to fix it doing:

recovery.conf:
restore_command = 'cp /var/lib/pgsql/archive/%f %p'
recovery_target_timeline = 'latest'
standby_mode = off
trigger_file = '/tmp/pg_failover_trigger'

Then, I got the error:
FATAL:  archive file "00000002000019D5000000EC" has wrong size: 0 instead of 16777216

To fix it:

rm 00000002000019D5000000EC


Restart postgres and then:
 LOG:  archive recovery complete
LOG:  database system is ready to accept connections 

pgsql-general by date:

Previous
From: Michael Paquier
Date:
Subject: Re: Validity of using the test_decoding plugin for production?
Next
From: david.turon@linuxbox.cz
Date:
Subject: ENABLE ROW LEVEL SECURITY cause huge produce of checkpoints