From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Lonni J Friedman <netllama(at)gmail(dot)com> |
Cc: | Jeff Davis <pgsql(at)j-davis(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: pg_upgrade + streaming replication ? |
Date: | 2012-03-20 18:58:20 |
Message-ID: | 20120320185820.GA26163@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Tue, Mar 20, 2012 at 11:56:29AM -0700, Lonni J Friedman wrote:
> >> So how can you resume streaming without rebuilding the slaves?
> >
> > Oh, wow, I never thought of the fact that the system tables will be
> > different? I guess you could assume the pg_dump restore is going to
> > create things exactly the same on all the systems, but I never tested
> > that. Do the system id's have to match? That would be a problem
> > because you are initdb'ing on each server. OK, crazy idea, but I
> > wonder if you could initdb on the master, then copy that to the slaves,
> > then run pg_upgrade on each of them. Obviously this needs some testing.
>
> Wouldn't it be easier to just pg_upgrade the master, then setup the
> slaves from scratch (with rsync, etc)? It certainly wouldn't be any
> more work to do it that way (although still a lot more work than
> simply running pg_upgrade on all servers).
Hey, wow, that is an excellent idea because rsync is going to realize
that all the user-data files are exactly the same and skip them --- that
is the winner solution. I should probably add this to the pg_upgrade
documentaiton. Thanks.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
From | Date | Subject | |
---|---|---|---|
Next Message | Merlin Moncure | 2012-03-20 19:07:10 | Re: [GENERAL] Altering a table with a rowtype column |
Previous Message | Lonni J Friedman | 2012-03-20 18:56:29 | Re: pg_upgrade + streaming replication ? |