| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net> |
| 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 17:27:27 |
| Message-ID: | 20120710172727.GE8689@momjian.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
| Attachment | Content-Type | Size |
|---|---|---|
| pg_upgrade.diff | text/x-diff | 755 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Sabino Mullane | 2012-07-10 17:35:28 | Re: Btree or not btree? That is the question |
| Previous Message | Magnus Hagander | 2012-07-10 17:06:39 | Re: Using pg_upgrade on log-shipping standby servers |