| From: | "Nicholson, Brad (Toronto, ON, CA)" <bnicholson(at)hp(dot)com> |
|---|---|
| To: | francis picabia <fpicabia(at)gmail(dot)com> |
| Cc: | "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: Best practise for upgrade of 24GB+ database |
| Date: | 2012-01-23 13:10:26 |
| Message-ID: | EC55DC235432104F8255702A8D7344D925739880@G9W0741.americas.hpqcorp.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
> -----Original Message-----
> From: francis picabia [mailto:fpicabia(at)gmail(dot)com]
> Sent: Friday, January 20, 2012 3:39 PM
> To: Nicholson, Brad (Toronto, ON, CA)
> Cc: pgsql-admin(at)postgresql(dot)org
> Subject: Re: [ADMIN] 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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Al-Salami, Adel | 2012-01-23 13:56:09 | "service user account 'postgres' could not be created" |
| Previous Message | Kevin Grittner | 2012-01-22 17:51:31 | Re: Force explicit transactions on insert / update |