From: | Venkata Balaji N <nag1010(at)gmail(dot)com> |
---|---|
To: | fredrik(at)huitfeldt(dot)com |
Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Streaming replication, master recycling |
Date: | 2016-05-14 07:38:51 |
Message-ID: | CAEyp7J-hgiQgjhE2wSKyWJy21joXQyePgEAHPsWnd5Jvz0hu7g@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Wed, May 11, 2016 at 9:04 PM, <fredrik(at)huitfeldt(dot)com> wrote:
> I apologise for the missing data.
>
> we are running 9.1.15 on debian servers.
>
There is a possibility of making the old master standby if you have
promoted standby after clean-shutting down the master. I I tested this in
9.2.x and later versions. This is a manual process in 9.2, i think it is
the same in 9.1.x version as well.
The process is -
- Ensure master and standby are in sync before switching over
- Promote standby
- build recovery.conf at old master with the parameter
recovery_target_timeline set to 'latest'
- When you start the old master, it will ask for timeline history files
which you need to manually transfer from new master
- The old master must become standby
Hope this helps and works in 9.1.x
Regards,
Venkata B N
Fujitsu Australia
From | Date | Subject | |
---|---|---|---|
Next Message | Alex Magnum | 2016-05-14 11:33:29 | Keeping top N records of a group |
Previous Message | Peter J. Holzer | 2016-05-14 07:38:31 | Re: Using both ident and password in pg_hba.conf |