From: Bruce Momjian <bruce@momjian.us>
To: christian.echerer@manroland-web.com
Cc: pgsql-admin@postgresql.org
Subject: Re: Missing timeline history file after execution of pg_upgrade
Date: Sat, 6 Dec 2014 09:07:08 -0500
Message-ID: <20141206140708.GA28234@momjian.us> (raw)
In-Reply-To: <D5359E0908278642BB1747131D62694DAB22560F@AUSMXMBX01.mrws.biz>
References: <D5359E0908278642BB1747131D62694DAB22560F@AUSMXMBX01.mrws.biz>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>
On Mon, Nov 10, 2014 at 01:48:40PM +0000, christian.echerer@manroland-web.com wrote:
> I have three questions:
> 1) Why pg_upgrade changed the timeline informations?
> 2) How do I get replication (Database B -> Database C) working?
> 3) Is this behavior intended. Is there a workaround for me?
You need to create new standbys after the upgrade --- pg_upgrade does
not retain the WAL files from the previous cluster, as the format might
have changed.
--
Bruce Momjian <bruce@momjian.us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ Everyone has their own god. +
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
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: bruce@momjian.us, christian.echerer@manroland-web.com
Subject: Re: Missing timeline history file after execution of pg_upgrade
In-Reply-To: <20141206140708.GA28234@momjian.us>
* 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