From: | Shreeyansh Dba <shreeyansh2014(at)gmail(dot)com> |
---|---|
To: | M Jane <mskiesewetter(at)gmail(dot)com> |
Cc: | pgsql-admin <pgsql-admin(at)postgresql(dot)org>, Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Postgresql 9.6.12 switchover failing |
Date: | 2019-03-08 16:40:15 |
Message-ID: | CAGDYbUNmHALVC_w=ibtM8sovJ=L-2DhtTFPrcjiG3ESKa22Qxg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Hi Marian,
Yes, We have faced the same issue, generally, this type of issue occurs due
to missing of history file i.e(00000000.history) during the replication
setup using the pg_basebackup.
To resolve this type issue you need to create an empty history file with
name 00000000.history on the master server then rebuild old master by
initiating the pg_basebackup.
Hope this helps.
Thanks & Regards,
*Shreeyansh DBA Team*
www.shreeyansh.com
On Fri, Mar 8, 2019 at 8:11 PM M Jane <mskiesewetter(at)gmail(dot)com> wrote:
> Hi everyone,
>
> I have a strange issue on my testing postgresql cluster.
> I have 2 nodes with postgresql 9.6.12 on RHEL7 .
> The slave is being updated through hotstandby streaming replication.
>
> In the past ( 9.6.8 and earlier), I was able to do a clean switchover
> without any issues.
> I did the following steps:
> 1. Check if the standby is uptodate
> 2. If so, shutdown the primary
> 3. pg_ctl promote the standby
> 4. Create a recovery.conf on the former primary and start the instance.
>
> This worked just fine, with in the end the roles of the nodes changed.
>
> Now I have version 9.6.12 and am trying to do the same.
> The steps 1 to 3 works just fine.
> But bringing up the old primary as a slave doesn't work. I get errors (
> like >FATAL: requested timeline 5 is not a child of this server's history)
> and the instances shuts down automatically.
> I know I can fix it with pg_rewind ( have done it), but am confused about
> this.
>
> Does anyone have the same issue? Or has anyone encountered the same
> problem?
>
> Thanks in advance.
> regards,
> Marian
>
>
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Gierth | 2019-03-08 16:51:47 | Re: Upgrade 10.5->10.6 : db crash BUS ERROR (sig 10), reproducible |
Previous Message | Peter | 2019-03-08 16:26:15 | Re: Upgrade 10.5->10.6 : db crash BUS ERROR (sig 10), reproducible |