| From: | Glyn Astill <glynastill(at)yahoo(dot)co(dot)uk> |
|---|---|
| To: | Murthy Nunna <mnunna(at)fnal(dot)gov>, Venkata Balaji Nagothi <vbnpgc(at)gmail(dot)com> |
| 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 13:25:40 |
| Message-ID: | 1395149140.23656.YahooMailNeo@web133203.mail.ir2.yahoo.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
> From: Murthy Nunna <mnunna(at)fnal(dot)gov>
>To: Venkata Balaji Nagothi <vbnpgc(at)gmail(dot)com>
>Cc: "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org>
>Sent: Tuesday, 18 March 2014, 12:49
>Subject: Re: [ADMIN] pg_upgrade in primary/standby architecture
>
>
>
>Hi Venkata Balaji,
>
>Thank you!
>
>Yes, streaming replication cannot be setup between two different versions. That is true.
>
>I am looking to upgrade both primary and standby with minimal outage to application….. I want to know if it is possible. If it is not possible, is there any architecture where we can minimize upgrade related outage?
>
You could use Slony-I for this, and it should be fairly quick to set up now that as of 2.2 you can add multiple tables and sequences in one go with SET ADD TABLE.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gilberto Castillo | 2014-03-18 14:38:06 | Re: pg_upgrade in primary/standby architecture |
| Previous Message | Murthy Nunna | 2014-03-18 12:49:16 | Re: pg_upgrade in primary/standby architecture |