Re: pg_upgrade in primary/standby architecture

From: "Gilberto Castillo" <gilberto(dot)castillo(at)etecsa(dot)cu>
To: "Glyn Astill" <glynastill(at)yahoo(dot)co(dot)uk>
Cc: "Murthy Nunna" <mnunna(at)fnal(dot)gov>, "Venkata Balaji Nagothi" <vbnpgc(at)gmail(dot)com>, "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org>
Subject: Re: pg_upgrade in primary/standby architecture
Date: 2014-03-18 14:38:06
Message-ID: 37084.192.168.207.54.1395153486.squirrel@webmail.etecsa.cu
Views: Raw Message | Whole Thread | 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.

I have a small guide that can be useful.

Saludos,
Gilberto Castillo
La Habana, Cuba

Attachment Content-Type Size
unknown_filename text/plain 179 bytes

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Kasia Tuszynska 2014-03-18 16:14:09 Re: looking for doc
Previous Message Glyn Astill 2014-03-18 13:25:40 Re: pg_upgrade in primary/standby architecture