From: Steve Crawford <scrawford@pinpointresearch.com>
To: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
Subject: Upgrading and streaming replication
Date: Tue, 25 Sep 2012 14:22:46 -0700
Message-ID: <506220A6.5020907@pinpointresearch.com> (raw)
I'm planning my upgrade from 9.1.5 to 9.1.6 on some master and
streaming-replication standby pairs and have some questions:
Generally:
http://www.postgresql.org/docs/9.1/static/warm-standby.html section
25.2.1 says:
"...it is likely that running different minor release levels on primary
and standby servers will work successfully. However, no formal support
for that is offered and you are advised to keep primary and standby
servers at the same release level as much as possible. When updating to
a new minor release, the safest policy is to update the standby servers
first — a new minor release is more likely to be able to read WAL files
from a previous minor release than vice versa."
My mental translation of this is "...try updating the standby first and
hope it works - if not and you at some point find your standby is scrod,
you're on your own...we warned you..."
Is this the correct interpretation? I'd feel better if there were a
documented approved upgrade process for systems using streaming
replication and that the release notes would specify when a minor
upgrade involves WAL file changes that require special handling (and it
would be nice if PostgreSQL would detect dangerous format mismatch
issues and refuse to start).
Specifically:
Neither the update release notes on the wiki
(http://wiki.postgresql.org/wiki/20120924updaterelease as of this
writing) nor the release notes
http://www.postgresql.org/docs/9.1/static/release-9-1-6.html nor news
http://www.postgresql.org/about/news/1416/ indicate that any special
handling is required on standby servers. Can anyone confirm if that is
correct or, if not, what additional steps are prudent?
Cheers,
Steve
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: scrawford@pinpointresearch.com
Subject: Re: Upgrading and streaming replication
In-Reply-To: <506220A6.5020907@pinpointresearch.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