From: | Devrim GÜNDÜZ <devrim(at)gunduz(dot)org> |
---|---|
To: | Steve Crawford <scrawford(at)pinpointresearch(dot)com> |
Cc: | "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: Upgrading and streaming replication |
Date: | 2012-09-25 21:44:46 |
Message-ID: | 1348609486.3516.30.camel@lenovo01-laptop03.gunduz.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Hi,
On Tue, 2012-09-25 at 14:22 -0700, Steve Crawford wrote:
> "...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..."
I would translate it as: "Newer minor releases will be compatible with
the previous versions, so receving xlogs from older releases will be
supported. Upgrade standby first, and then the master server"
Regards,
--
Devrim GÜNDÜZ
Principal Systems Engineer @ EnterpriseDB: http://www.enterprisedb.com
PostgreSQL Danışmanı/Consultant, Red Hat Certified Engineer
Community: devrim~PostgreSQL.org, devrim.gunduz~linux.org.tr
http://www.gunduz.org Twitter: http://twitter.com/devrimgunduz
From | Date | Subject | |
---|---|---|---|
Next Message | Fujii Masao | 2012-09-26 00:01:52 | Re: WAL recovery failure |
Previous Message | Steve Crawford | 2012-09-25 21:22:46 | Upgrading and streaming replication |