Re: Using pg_upgrade on log-shipping standby servers - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: Using pg_upgrade on log-shipping standby servers
Date
Msg-id 20120711030837.GA21948@momjian.us
Whole thread Raw
In response to Re: Using pg_upgrade on log-shipping standby servers  (Magnus Hagander <magnus@hagander.net>)
List pgsql-hackers
On Tue, Jul 10, 2012 at 09:10:25PM +0200, Magnus Hagander wrote:
> On Tue, Jul 10, 2012 at 7:27 PM, Bruce Momjian <bruce@momjian.us> wrote:
> > On Tue, Jul 10, 2012 at 07:06:39PM +0200, Magnus Hagander wrote:
> >> >> >> rsync where and how? What are you actually trying to suggest people
> >> >> >> do?
> >> >> >
> >> >> > Updated docs attached.
> >> >>
> >> >> I suggest just removing the rsync part completely. You're basically
> >> >> saying "you ca nset up a new standby after you're done", which is kind
> >> >> of obvious anyway. And if you're going to use rsync fromthe master to
> >> >> make a new standby, there's no point in running pg_upgrade on the new
> >> >> standby in the first place.
> >> >
> >> > I went the other direction and just said you can't upgrade a standby (as
> >> > a standby), and to just use rsync --- patch attached.
> >>
> >> Reads much better now. I'd say "use rsync to rebuild the standbys",
> >> but that's more nitpicking :) (And maybe "the simplest way" rather
> >> than "the simplest case"? But i'll leave that to someone who has
> >> english as their first language)
> >
> > Both change made;  updated patch attached.
> 
> Looks good to me.

OK, applied and backpatched to 9.2.

--  Bruce Momjian  <bruce@momjian.us>        http://momjian.us EnterpriseDB
http://enterprisedb.com
 + It's impossible for everything to be true. +


pgsql-hackers by date:

Previous
From: Tatsuo Ishii
Date:
Subject: Re: Patch: add conversion from pg_wchar to multibyte
Next
From: Tom Lane
Date:
Subject: Re: BlockNumber initialized to InvalidBuffer?