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 {} postg...@momjian.us:/u/pgsql/data \; -- Bruce Momjian <br...@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + It's impossible for everything to be true. + -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers