| From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | Patrick B <patrickbakerbr(at)gmail(dot)com> |
| Cc: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Turning slave into a master - PostgreSQL 9.2 |
| Date: | 2016-11-02 01:13:06 |
| Message-ID: | CAOR=d=36P049T8wHeptsUhfL7U54b3uzvDtz1CCjoRMXEzFfzg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tue, Nov 1, 2016 at 1:43 PM, Patrick B <patrickbakerbr(at)gmail(dot)com> wrote:
>
>
> 2016-11-02 2:55 GMT+13:00 Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>:
>>
>> On Mon, Oct 31, 2016 at 8:01 PM, Patrick B <patrickbakerbr(at)gmail(dot)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!
Huh, after a pg_basebackup all you should need is a recovery.conf in
place and a trigger file.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Suomela Tero | 2016-11-02 12:11:59 | Replication (BDR) problem: won't catch up after connection timeout |
| Previous Message | Patrick B | 2016-11-02 00:48:35 | Re: Turning slave into a master - PostgreSQL 9.2 |