From: Bruce Momjian <bruce@momjian.us>
To: 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: Tue, 12 Sep 2017 17:52:02 -0400
Message-ID: <20170912215202.GA6766@momjian.us> (raw)
In-Reply-To: <VisenaEmail.66.44a2ed6a4130e92c.15e776c27e4@tc7-visena>
References: <20170912171922.GA3705@momjian.us>
<VisenaEmail.66.44a2ed6a4130e92c.15e776c27e4@tc7-visena>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>
On Tue, Sep 12, 2017 at 08:59:05PM +0200, Andreas Joseph Krogh wrote:
> Improvements?
>
> Thanks, that certainly improves things.
> But; I still find the rsync-command in f) confusing;
> 1. Why --size-only? From rsync manual: "skip files that match in size", is this
> safe??
> 2. Why is old_pgdata in the rsync-command, why is it needed to sync it?
If the file exists under the same name, it doesn't need to be checked at
all --- it is the same. We don't want to check the file modification
time because it will probably be different because of replay delay or
clock drift. We could use checksums, but there is no need since there is
no way the file contents could be different.
> There are many ways to do/configure things it seems, resulting in many ifs and
> buts which makes section 10 rather confusing. I really think a complete
> example, with absolute paths, would be clarifying.
You mean a full rsync command, e.g.:
rsync --archive --delete --hard-links --size-only \
/opt/PostgreSQL/9.5 /opt/PostgreSQL/9.6 standby:/opt/PostgreSQL
Does that help?
--
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
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, 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: <20170912215202.GA6766@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