From: Andy Colson <andy@squeakycode.net>
To: pgsql-general@postgresql.org
Subject: Re: 9.5 beta pg_upgrade documentation
Date: Sun, 23 Aug 2015 09:45:50 -0500
Message-ID: <55D9DC9E.8080806@squeakycode.net> (raw)
In-Reply-To: <55D789B5.7040308@squeakycode.net>
References: <55D789B5.7040308@squeakycode.net>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-general>
I think we should add a step 6.5 (before step 7 Stop both servers) with something like:
If you are upgrading both a primary and standby, then we need to make sure the standby is caught up.
If you are wal shipping then on primary run: select pg_switch_xlog();
shut down primary
before you shut down the standby make sure it gets caught up to the primary.
I don't think its 100% required for them to be exact, is it? If they are a little different then rsync has more data to xfer from primary to standby ... but it would still work. Right?
-Andy
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
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-general@postgresql.org
Cc: andy@squeakycode.net
Subject: Re: 9.5 beta pg_upgrade documentation
In-Reply-To: <55D9DC9E.8080806@squeakycode.net>
* 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