| From: | Venkata Balaji Nagothi <vbnpgc(at)gmail(dot)com> |
|---|---|
| To: | Murthy Nunna <mnunna(at)fnal(dot)gov> |
| Cc: | "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: pg_upgrade in primary/standby architecture |
| Date: | 2014-03-18 05:46:59 |
| Message-ID: | CAHBAh5thJrGVi16X46yTdrt2cF6V4ZuJ8MvUonhbzcOo_eDvzg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Tue, Mar 18, 2014 at 1:52 PM, Murthy Nunna <mnunna(at)fnal(dot)gov> wrote:
> I am wondering if there is a way we can leverage replication set up to
> minimize outage caused by pg_upgrade in case of major version upgrade. We
> use streaming replication.
>
If i got you correct - Streaming Replication cannot be setup between two
different versions of PostgreSQL.
> Scenario:
>
> 1. Primary and standby are running 9.1.6 and I want to upgrade both
> to 9.2.4 (or 9.2.6)
>
Though its not an straight forward or easy way to upgrade a big database -
Did you think of Slony as an option ?
We have used Slony in the past to upgrade databases to reduce lengthy
downtime. This depends on lot of factors though.
Regards.
Venkata Balaji N
Sr. Database Administrator
Fujitsu Australia
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Murthy Nunna | 2014-03-18 12:49:16 | Re: pg_upgrade in primary/standby architecture |
| Previous Message | Murthy Nunna | 2014-03-18 02:52:34 | pg_upgrade in primary/standby architecture |