Re: Clarification in pg10's pgupgrade.html step 10 (upgrading standby servers)

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Stephen Frost <sfrost(at)snowman(dot)net>
Cc: Andreas Joseph Krogh <andreas(at)visena(dot)com>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Clarification in pg10's pgupgrade.html step 10 (upgrading standby servers)
Date: 2017-09-16 16:02:20
Message-ID: 20170916160220.GD9874@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-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(at)momjian(dot)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 +

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andreas Joseph Krogh 2017-09-16 16:11:17 Re: Clarification in pg10's pgupgrade.html step 10 (upgrading standby servers)
Previous Message Bruce Momjian 2017-09-16 15:24:14 Re: Clarification in pg10's pgupgrade.html step 10 (upgrading standby servers)