pg.ddx.io pgsql-admin@postgresql.org mailing list archive
help / color / mirror / Atom feedpg_upgrade in primary/standby architecture
6+ messages / 4 participants
[nested] [flat]
* pg_upgrade in primary/standby architecture
@ 2014-03-18 02:52 Murthy Nunna <mnunna@fnal.gov>
2014-03-18 05:46 ` Re: pg_upgrade in primary/standby architecture Venkata Balaji Nagothi <vbnpgc@gmail.com>
0 siblings, 1 reply; 6+ messages in thread
From: Murthy Nunna @ 2014-03-18 02:52 UTC (permalink / raw)
To: pgsql-admin
Hello PGAdmins,
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.
Scenario:
1. Primary and standby are running 9.1.6 and I want to upgrade both to 9.2.4 (or 9.2.6)
2. Streaming replication is used
3. I cannot use pg_dump due to the size of the database. I have to use pg_upgrade
Thanks,
Murthy
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: pg_upgrade in primary/standby architecture
2014-03-18 02:52 pg_upgrade in primary/standby architecture Murthy Nunna <mnunna@fnal.gov>
@ 2014-03-18 05:46 ` Venkata Balaji Nagothi <vbnpgc@gmail.com>
2014-03-18 12:49 ` Re: pg_upgrade in primary/standby architecture Murthy Nunna <mnunna@fnal.gov>
0 siblings, 1 reply; 6+ messages in thread
From: Venkata Balaji Nagothi @ 2014-03-18 05:46 UTC (permalink / raw)
To: Murthy Nunna <mnunna@fnal.gov>; +Cc: pgsql-admin
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
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: pg_upgrade in primary/standby architecture
2014-03-18 02:52 pg_upgrade in primary/standby architecture Murthy Nunna <mnunna@fnal.gov>
2014-03-18 05:46 ` Re: pg_upgrade in primary/standby architecture Venkata Balaji Nagothi <vbnpgc@gmail.com>
@ 2014-03-18 12:49 ` Murthy Nunna <mnunna@fnal.gov>
2014-03-18 13:25 ` Re: pg_upgrade in primary/standby architecture Glyn Astill <glynastill@yahoo.co.uk>
2014-03-18 23:14 ` Re: pg_upgrade in primary/standby architecture Venkata Balaji Nagothi <vbnpgc@gmail.com>
0 siblings, 2 replies; 6+ messages in thread
From: Murthy Nunna @ 2014-03-18 12:49 UTC (permalink / raw)
To: Venkata Balaji Nagothi <vbnpgc@gmail.com>; +Cc: 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<mailto: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
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: pg_upgrade in primary/standby architecture
2014-03-18 02:52 pg_upgrade in primary/standby architecture Murthy Nunna <mnunna@fnal.gov>
2014-03-18 05:46 ` Re: pg_upgrade in primary/standby architecture Venkata Balaji Nagothi <vbnpgc@gmail.com>
2014-03-18 12:49 ` Re: pg_upgrade in primary/standby architecture Murthy Nunna <mnunna@fnal.gov>
@ 2014-03-18 13:25 ` Glyn Astill <glynastill@yahoo.co.uk>
2014-03-18 14:38 ` Re: pg_upgrade in primary/standby architecture Gilberto Castillo <gilberto.castillo@etecsa.cu>
1 sibling, 1 reply; 6+ messages in thread
From: Glyn Astill @ 2014-03-18 13:25 UTC (permalink / raw)
To: Murthy Nunna <mnunna@fnal.gov>; Venkata Balaji Nagothi <vbnpgc@gmail.com>; +Cc: pgsql-admin
> From: Murthy Nunna <mnunna@fnal.gov>
>To: Venkata Balaji Nagothi <vbnpgc@gmail.com>
>Cc: "pgsql-admin@postgresql.org" <pgsql-admin@postgresql.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.
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: pg_upgrade in primary/standby architecture
2014-03-18 02:52 pg_upgrade in primary/standby architecture Murthy Nunna <mnunna@fnal.gov>
2014-03-18 05:46 ` Re: pg_upgrade in primary/standby architecture Venkata Balaji Nagothi <vbnpgc@gmail.com>
2014-03-18 12:49 ` Re: pg_upgrade in primary/standby architecture Murthy Nunna <mnunna@fnal.gov>
2014-03-18 13:25 ` Re: pg_upgrade in primary/standby architecture Glyn Astill <glynastill@yahoo.co.uk>
@ 2014-03-18 14:38 ` Gilberto Castillo <gilberto.castillo@etecsa.cu>
0 siblings, 0 replies; 6+ messages in thread
From: Gilberto Castillo @ 2014-03-18 14:38 UTC (permalink / raw)
To: Glyn Astill <glynastill@yahoo.co.uk>; +Cc: Murthy Nunna <mnunna@fnal.gov>; Venkata Balaji Nagothi <vbnpgc@gmail.com>; pgsql-admin
>
>
>
>> From: Murthy Nunna <mnunna@fnal.gov>
>>To: Venkata Balaji Nagothi <vbnpgc@gmail.com>
>>Cc: "pgsql-admin@postgresql.org" <pgsql-admin@postgresql.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.
I have a small guide that can be useful.
Saludos,
Gilberto Castillo
La Habana, Cuba
---
This message was processed by Kaspersky Mail Gateway 5.6.28/RELEASE running at host imx3.etecsa.cu
Visit our web-site: <http://www.kaspersky.com;, <http://www.viruslist.com;
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: pg_upgrade in primary/standby architecture
2014-03-18 02:52 pg_upgrade in primary/standby architecture Murthy Nunna <mnunna@fnal.gov>
2014-03-18 05:46 ` Re: pg_upgrade in primary/standby architecture Venkata Balaji Nagothi <vbnpgc@gmail.com>
2014-03-18 12:49 ` Re: pg_upgrade in primary/standby architecture Murthy Nunna <mnunna@fnal.gov>
@ 2014-03-18 23:14 ` Venkata Balaji Nagothi <vbnpgc@gmail.com>
1 sibling, 0 replies; 6+ messages in thread
From: Venkata Balaji Nagothi @ 2014-03-18 23:14 UTC (permalink / raw)
To: Murthy Nunna <mnunna@fnal.gov>; +Cc: pgsql-admin
On Tue, Mar 18, 2014 at 11:49 PM, Murthy Nunna <mnunna@fnal.gov> wrote:
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?
>
In my previous email, i suggested/asked the possibility of using Slony
replication in your environment. It depends on lot of factors (database
size, number of tables, pl/pgsql code etc..) though. Please let us know
your thoughts on this. We can probably move further on this discussion.
Venkata Balaji N
Sr. Database Administrator
Fujitsu Australia
^ permalink raw reply [nested|flat] 6+ messages in thread
end of thread, other threads:[~2014-03-18 23:14 UTC | newest]
Thread overview: 6+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2014-03-18 02:52 pg_upgrade in primary/standby architecture Murthy Nunna <mnunna@fnal.gov>
2014-03-18 05:46 ` Venkata Balaji Nagothi <vbnpgc@gmail.com>
2014-03-18 12:49 ` Murthy Nunna <mnunna@fnal.gov>
2014-03-18 13:25 ` Glyn Astill <glynastill@yahoo.co.uk>
2014-03-18 14:38 ` Gilberto Castillo <gilberto.castillo@etecsa.cu>
2014-03-18 23:14 ` Venkata Balaji Nagothi <vbnpgc@gmail.com>
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