On Sat, Jul 21, 2012 at 8:57 AM, Bruce Momjian <br...@momjian.us> wrote:
> 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 \;
Relying on the number of hard links seems very fragile. For example,
it'll break if you are using copy mode. And it won't work on Windows,
either.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
