From: | Jeff Davis <pgsql(at)j-davis(dot)com> |
---|---|
To: | Bruce Momjian <bruce(at)momjian(dot)us> |
Cc: | Lonni J Friedman <netllama(at)gmail(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: pg_upgrade + streaming replication ? |
Date: | 2012-03-19 22:07:02 |
Message-ID: | 1332194822.1453.4.camel@sussancws0025 |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Mon, 2012-03-19 at 15:30 -0400, Bruce Momjian wrote:
> On Thu, Mar 01, 2012 at 02:01:31PM -0800, Lonni J Friedman wrote:
> > I've got a 3 node cluster (1 master/2 slaves) running 9.0.x with
> > streaming replication. I'm in the planning stages of upgrading to
> > 9.1.x, and am looking into the most efficient way to do the upgrade
> > with the goal of minimizing downtime & risk. After googling, the only
> > discussion that I've found of using pg_upgrade with a streaming
> > replication setup seems to be this (nearly) year old thread:
> > http://web.archiveorange.com/archive/v/9FNVlDWGQtpyWVL54jlK
> >
> > In summary, there is no way to use both pg_upgrade and streaming
> > replication simultaneously. I'd have to either use pg_upgrade and
> > then effectively rebuild/redeploy the slaves, or not use pg_upgrade,
> > and reimport all of the data. Is that still the latest status, or are
> > there other options?
>
> You can shut down all three servers, run pg_upgrade on all of them, then
> restart them as 9.1 servers.
After running pg_upgrade on each server individually, they will have
different system IDs, and potentially different on-disk representation
of the catalogs, right?
So how can you resume streaming without rebuilding the slaves?
Regards,
Jeff Davis
From | Date | Subject | |
---|---|---|---|
Next Message | Merlin Moncure | 2012-03-19 22:31:40 | Re: nice'ing the postgres COPY backend process to make pg_dumps run more "softly" |
Previous Message | Bill Moran | 2012-03-19 21:55:27 | Re: Anonymized database dumps |