pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Bruce Momjian <bruce@momjian.us>
To: Stephen Frost <sfrost@snowman.net>
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: Sat, 16 Sep 2017 12:02:20 -0400
Message-ID: <20170916160220.GD9874@momjian.us> (raw)
In-Reply-To: <20170914191250.GB6595@momjian.us>
References: <20170912230020.GD6766@momjian.us>
	<VisenaEmail.6c.c0e592c5af4ef0a2.15e785dcb61@tc7-visena>
	<20170913132627.GG6766@momjian.us>
	<20170913161633.GW4628@tamriel.snowman.net>
	<20170914191250.GB6595@momjian.us>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>

On Thu, Sep 14, 2017 at 03:12:50PM -0400, Bruce Momjian wrote:
> I talked with Stephen about this on IM.  The issue is that if you don't
> do --delete, and there are files in the primary that are not in the
> standby, they are copied, but files in the standby and not in the
> primary are kept.  This could lead to mixed primary/standby log files,
> or worse.  Using --delete means the new standby exactly matches the new
> primary and all the steps you need to adjust after a base backup are the
> same.
> 
> I added a mention of rsync --dry-run per Stephen's suggestion.
> 
> I have also added a paragraph from Magnus that I developed via IM that
> explains that you can use rsync to upgrade one standby from another
> standby, if the standby has not been started.

Patch applied through 9.5.  Updated docs at:

	http://momjian.us/pgsql_docs/pgupgrade.html

-- 
  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

+ As you are, so once was I.  As I am, so you will be. +
+                      Ancient Roman grave inscription +


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



view thread (39+ messages)  latest in thread

Message-ID: <20170916160220.GD9874@momjian.us>
Permalink:  ../20170916160220.GD9874@momjian.us/
Also on:    postgresql.org/message-id/20170916160220.GD9874@momjian.us

 · 

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-hackers@postgresql.org
  Cc: bruce@momjian.us, sfrost@snowman.net, 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: <20170916160220.GD9874@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