Re: Best practise for upgrade of 24GB+ database

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> -----Original Message-----
> From: francis picabia [mailto:fpicabia@xxxxxxxxx]
> Sent: Friday, January 20, 2012 3:39 PM
> To: Nicholson, Brad (Toronto, ON, CA)
> Cc: pgsql-admin@xxxxxxxxxxxxxx
> Subject: Re:  Best practise for upgrade of 24GB+ database
> > In the past I've used Slony to upgrade much larger database clusters
> than yours with minimal down time (I'm talking seconds for the actual
> master switch).  You set up a new replica on the new version and then
> move the master from old to new.  No need to explicitly resync
> afterwards.
> 
> That's great information.  9.0 is introducing streaming replication,
> so that is another option I'll look into.

Streaming rep will not help you here as you cannot replicated between versions with it.  Slony allows replication to a new version.

Brad.

-- 
Sent via pgsql-admin mailing list (pgsql-admin@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin



[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]

  Powered by Linux