From: Charles Sprickman <spork@biglist.com>
To: pgsql-admin@postgresql.org
Subject: upgrades and streaming replication
Date: Tue, 10 Sep 2013 23:13:24 -0400
Message-ID: <BF48DCBA-CA71-4BF2-94CB-D95FD6909D6C@biglist.com> (raw)
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>
I just wanted to check if there are any updates on the preferred way to upgrade a group of servers that are using streaming replication with minimal downtime.
Mailing list messages from a year or two ago pretty much state the following:
* No current plans to come up with some new mechanism to automate this process, downtime is assumed.
* If you want no downtime, use one of the userspace replication solutions.
* Best option is to upgrade the master with pg_upgrade, then upgrade the slaves and re-copy your data.
* While it's tempting to think you could just run pg_upgrade on all hosts to avoid the copy step, that will not work as something in the system catalog changes which will break replication.
* No good options to speed up the slave copy - rsync will either use timestamps to figure out if a file changed (and streaming skews that), or checksumming (and checksumming is slow).
Is that still pretty much the situation today with 9.2 and 9.3?
Any good guides or BCPs for the standard procedure that emphasize limiting downtime and giving a good rollback path?
Thanks,
Charles
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
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-admin@postgresql.org
Cc: spork@biglist.com
Subject: Re: upgrades and streaming replication
In-Reply-To: <BF48DCBA-CA71-4BF2-94CB-D95FD6909D6C@biglist.com>
* 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