From: | Magnus Hagander <magnus(at)hagander(dot)net> |
---|---|
To: | Bruce Momjian <bruce(at)momjian(dot)us> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Using pg_upgrade on log-shipping standby servers |
Date: | 2012-07-10 19:10:25 |
Message-ID: | CABUevEx499c3GwzRn=vDBmgOWF4hxDsfxM=by+N5UOcTbTtimg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Jul 10, 2012 at 7:27 PM, Bruce Momjian <bruce(at)momjian(dot)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.
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2012-07-10 19:28:18 | Re: enhanced error fields |
Previous Message | Peter Geoghegan | 2012-07-10 18:56:40 | Re: enhanced error fields |