Re: pg_upgrade in primary/standby architecture
| От | Murthy Nunna |
|---|---|
| Тема | Re: pg_upgrade in primary/standby architecture |
| Дата | |
| Msg-id | BD7563973EF8894D905C80593EE9A4ED34B2F8@MAIL02.fnal.gov обсуждение исходный текст |
| Ответ на | Re: pg_upgrade in primary/standby architecture (Venkata Balaji Nagothi <vbnpgc@gmail.com>) |
| Ответы |
Re: pg_upgrade in primary/standby architecture
Re: pg_upgrade in primary/standby architecture |
| Список | pgsql-admin |
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?
Murthy
From: Venkata Balaji Nagothi [mailto:vbnpgc@gmail.com]
Sent: Tuesday, March 18, 2014 12:47 AM
To: Murthy Nunna
Cc: pgsql-admin@postgresql.org
Subject: Re: [ADMIN] pg_upgrade in primary/standby architecture
On Tue, Mar 18, 2014 at 1:52 PM, Murthy Nunna <mnunna@fnal.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
В списке pgsql-admin по дате отправления: