| From: | Abhinav Mehta <abhinav(at)metarain(dot)com> |
|---|---|
| To: | Richard Schmidt <Richard(dot)Schmidt(at)metservice(dot)com> |
| Cc: | "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Pg_rewind cannot load history wal |
| Date: | 2018-08-08 17:54:45 |
| Message-ID: | A3D97CAA-A2DF-42CC-A374-5743DAA99060@metarain.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Yes, consider using Repmgr.
> On 08-Aug-2018, at 3:20 AM, Richard Schmidt <Richard(dot)Schmidt(at)metservice(dot)com> wrote:
>
> We think we have found our missing step. We needed to do an ordered shutdown of the original primary before promoting the standby
> I.e.
>
> >1. Make some changes to the A (the primary) and check that they are replicated to the B (the standby)
>
> Missing step:
> Perform ordered shutdown of A (the primary)
>
> >2.Promote B to be the new primary
>
> This know means that we have this simple use-case working.
>
>
>
> This email and any attachments may contain confidential information. If you are not the intended recipient, your use or communication of the information is strictly prohibited. If you have received this message in error please notify MetService immediately.
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Luca Ferrari | 2018-08-09 07:00:25 | select version() with internal number version? |
| Previous Message | Peter Geoghegan | 2018-08-08 17:27:59 | Re: found xmin from before relfrozenxid on pg_catalog.pg_authid |