pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: dezso <avandras@gmail.com>
To: pgsql-admin@postgresql.org
Subject: Re: Missing timeline history file after execution of pg_upgrade
Date: Tue, 3 Feb 2015 02:36:37 -0700 (MST)
Message-ID: <1422956197919-5836521.post@n5.nabble.com> (raw)
In-Reply-To: <D5359E0908278642BB1747131D62694DB37B1A58@AUSMXMBX01.mrws.biz>
References: <D5359E0908278642BB1747131D62694DAB22560F@AUSMXMBX01.mrws.biz>
	<20141206140708.GA28234@momjian.us>
	<D5359E0908278642BB1747131D62694DB37B1A58@AUSMXMBX01.mrws.biz>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>

Just to confirm that this problem exists: we upgraded recently from 9.3 to
9.4 using pg_upgrade, having the slave rebuilt as prescribed.  Directly
after starting up the slave, we started getting the above mentioned error. 
Replication to this slave works otherwise.

Is there a way to get the history file back?  



--
View this message in context: http://postgresql.nabble.com/Missing-timeline-history-file-after-execution-of-pg-upgrade-tp5826326p5...
Sent from the PostgreSQL - admin mailing list archive at Nabble.com.


-- 
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin



view thread (8+ messages)  latest in thread

Message-ID: <1422956197919-5836521.post@n5.nabble.com>
Permalink:  ../1422956197919-5836521.post@n5.nabble.com/
Also on:    postgresql.org/message-id/1422956197919-5836521.post@n5.nabble.com

 · 

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: avandras@gmail.com
  Subject: Re: Missing timeline history file after execution of pg_upgrade
  In-Reply-To: <1422956197919-5836521.post@n5.nabble.com>

* 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