From: Michael Banck <michael.banck@credativ.de>
To: Stephen Frost <sfrost@snowman.net>
Cc: Bruce Momjian <bruce@momjian.us>
Cc: Andreas Joseph Krogh <andreas@visena.com>
Cc: Michael Paquier <michael.paquier@gmail.com>
Cc: Robert Haas <robertmhaas@gmail.com>
Cc: pgsql-hackers@postgresql.org <pgsql-hackers@postgresql.org>
Subject: Re: Clarification in pg10's pgupgrade.html step 10 (upgrading standby servers)
Date: Wed, 13 Sep 2017 19:39:31 +0200
Message-ID: <20170913173931.GA12194@nighthawk.caipicrew.dd-dns.de> (raw)
In-Reply-To: <20170912233840.GS4628@tamriel.snowman.net>
References: <20170912215202.GA6766@momjian.us>
<VisenaEmail.6b.4b17ca3ad0960052.15e782a53d1@tc7-visena>
<20170912230020.GD6766@momjian.us>
<20170912233840.GS4628@tamriel.snowman.net>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>
On Tue, Sep 12, 2017 at 07:38:40PM -0400, Stephen Frost wrote:
> Further, really, I think we should provide a utility to do all of the
> above instead of using rsync- and that utility should do some additional
> things, such as:
>
> - Check that the control file on the primary and replica show that they
> reached the same point prior to the pg_upgrade. If they didn't, then
> things could go badly as there's unplayed WAL that the primary got
> through and the replica didn't.
>
> - Not copy over unlogged data, or any other information that shouldn't
> be copied across.
>
> - Allow the directory structures to be more different between the
> primary and the replica than rsync allows (wouldn't have to have a
> common subdirectory on the replica).
>
> - Perhaps other validation checks or similar.
>
> Unfortunately, this is a bit annoying as it necessairly involves running
> things on both the primary and the replica from the same tool, without
> access to PG, meaning we'd have to work through something else (such as
> SSH, like rsync does, but then what would we do for Windows...?).
Maybe pg_rewind's mechanism could be partially reused for this as it
seems to accomplish something vaguely similar AIUI?
Michael
--
Michael Banck
Projektleiter / Senior Berater
Tel.: +49 2166 9901-171
Fax: +49 2166 9901-100
Email: michael.banck@credativ.de
credativ GmbH, HRB Mönchengladbach 12080
USt-ID-Nummer: DE204566209
Trompeterallee 108, 41189 Mönchengladbach
Geschäftsführung: Dr. Michael Meskes, Jörg Folz, Sascha Heuer
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
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-hackers@postgresql.org
Cc: michael.banck@credativ.de, sfrost@snowman.net, bruce@momjian.us, andreas@visena.com, michael.paquier@gmail.com, robertmhaas@gmail.com
Subject: Re: Clarification in pg10's pgupgrade.html step 10 (upgrading standby servers)
In-Reply-To: <20170913173931.GA12194@nighthawk.caipicrew.dd-dns.de>
* 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