From: | AI Rumman <rummandba(at)gmail(dot)com> |
---|---|
To: | Bruce Momjian <bruce(at)momjian(dot)us> |
Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Pg_upgrade remote copy |
Date: | 2015-09-06 01:37:21 |
Message-ID: | CAGoODpdqJiGTq7Lz-=OvBQCJ9k8zaxeoNqN8oG4fM4PW4+tzCA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Thanks for the solution.
On Wed, Sep 2, 2015 at 4:15 PM, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> On Wed, Sep 2, 2015 at 04:50:32PM -0300, Alvaro Herrera wrote:
> > Bruce Momjian wrote:
> > > On Fri, Aug 28, 2015 at 10:34:38PM -0700, AI Rumman wrote:
> >
> > > > In pg_upgrade, how about adding a feature to copy data directory
> over network.
> > > > That is, we can run pg_upgrade from our new host, where old host
> will be a
> > > > remote machine.
> >
> > > I think it is much simpler to just copy the old clsuter to the remote
> > > server and run pg_upgrade in --link mode on the remote server.
> >
> > Couldn't it run pg_basebackup as a first step?
>
> Yes. I was thinking it would be simpler to just shut down the server
> and copy it, but pg_basebackup would allow the server to be up during
> the copy.
>
> --
> Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
> EnterpriseDB http://enterprisedb.com
>
> + Everyone has their own god. +
>
From | Date | Subject | |
---|---|---|---|
Next Message | 周正中 (德歌) | 2015-09-06 02:04:27 | 答复:[HACKERS] about fsync in CLOG buffer write |
Previous Message | Greg Stark | 2015-09-06 00:58:54 | Re: Failing assertions in indxpath.c, placeholder.c and brin_minmax.c |