From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | Aidan Van Dyk <aidan(at)highrise(dot)ca>, Jeff Davis <pgsql(at)j-davis(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Using pg_upgrade on log-shipping standby servers |
Date: | 2012-07-21 12:57:36 |
Message-ID: | 20120721125736.GC27581@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sat, Jul 21, 2012 at 11:24:21AM +0300, Peter Eisentraut wrote:
> On fre, 2012-07-20 at 13:11 -0400, Bruce Momjian wrote:
> > I think the commands to run after pg_upgrade --link completes on both
> > primary and standby might be as easy as:
> >
> > cd /u/pg/pgsql.old/data
> > find . -links 1 -exec cp {} /u/pgsql/data \;
> >
> > Why would we want anything more complicated than this?
>
> In practice these are on different machines, and the way the machines
> are connected could vary wildly. So an automated solution might be
> difficult to find.
Yeah, I was thinking of just suggesting scp as a doc example and let
users adjust that:
cd /u/pg/pgsql.old/data
find . -links 1 -exec scp {} postgres(at)momjian(dot)us:/u/pgsql/data \;
--
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 | Peter Geoghegan | 2012-07-21 14:19:15 | Re: 9.2 release schedule |
Previous Message | Martijn van Oosterhout | 2012-07-21 08:55:57 | Re: Resetting libpq connections after an app error |