pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Jehan-Guillaume (ioguix) de Rorthais <ioguix@free.fr>
To: M Jane <mskiesewetter@gmail.com>
Cc: Shreeyansh Dba <shreeyansh2014@gmail.com>
Cc: Pgsql-admin <pgsql-admin@lists.postgresql.org>
Subject: Re: Postgresql 9.6.12 switchover failing
Date: Fri, 8 Mar 2019 17:51:49 +0100
Message-ID: <20190308175149.02edbcc0@firost> (raw)
In-Reply-To: <CAGDYbUNmHALVC_w=ibtM8sovJ=L-2DhtTFPrcjiG3ESKa22Qxg@mail.gmail.com>
References: <CANBd27KqYcdxSfmbyMDCSQLOkLKKrA0BeVwDHfXDbxOdqoa1JA@mail.gmail.com>
	<CAGDYbUNmHALVC_w=ibtM8sovJ=L-2DhtTFPrcjiG3ESKa22Qxg@mail.gmail.com>

On Fri, 8 Mar 2019 22:10:15 +0530
Shreeyansh Dba <shreeyansh2014@gmail.com> wrote:

> 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.

Uh, what? Do you have further info about this? I fail to understand how this is
related to OP question...

> On Fri, Mar 8, 2019 at 8:11 PM M Jane <mskiesewetter@gmail.com> wrote:
...
> > 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.

While doing a clean switchover, I never seen this (yet).

How are you checking both servers are up-to-date? Do you check that the standby
received everything from the old primary, including its shutdown checkpoint,
before promoting?

Make sure your standby staid connected to your old primary until the later is
completely shutdown-ed. Nothing should disconnect them during the whole
process. And make sure to use mode fast or smart to stop the old primary.

Are you able to share with us the restart checkpoint on the old
primary and the history file created by the new-primary? How far are the
restart LSN and timeline fork from each other?

Regards,




view thread (7+ messages)  latest in thread

Message-ID: <20190308175149.02edbcc0@firost>
Permalink:  ../20190308175149.02edbcc0@firost/
Also on:    postgresql.org/message-id/20190308175149.02edbcc0@firost

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: ioguix@free.fr, mskiesewetter@gmail.com, shreeyansh2014@gmail.com, pgsql-admin@lists.postgresql.org
  Subject: Re: Postgresql 9.6.12 switchover failing
  In-Reply-To: <20190308175149.02edbcc0@firost>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox