Re: pg_upgrade and rsync - Mailing list pgsql-hackers

From Jim Nasby
Subject Re: pg_upgrade and rsync
Date
Msg-id 54C81A8C.8030705@BlueTreble.com
Whole thread Raw
In response to Re: pg_upgrade and rsync  (Stephen Frost <sfrost@snowman.net>)
Responses Re: pg_upgrade and rsync
Re: pg_upgrade and rsync
List pgsql-hackers
On 1/27/15 9:29 AM, Stephen Frost wrote:
>> My point is that Bruce's patch suggests looking for "remote_dir" in
>> >the rsync documentation, but no such term appears there.
> Ah, well, perhaps we could simply add a bit of clarification to this:
>
> for details on specifying <option>remote_dir</>

The whole remote_dir discussion made me think of something... would --link-dest be any help here?
       --link-dest=DIR              This option behaves like --copy-dest, but unchanged files are hard linked from DIR
tothe des-              tination  directory.   The  files  must be identical in all preserved attributes (e.g. permis-
           sions, possibly ownership) in order for the files to be linked together.  An example:
 
                rsync -av --link-dest=$PWD/prior_dir host:src_dir/ new_dir/

-- 
Jim Nasby, Data Architect, Blue Treble Consulting
Data in Trouble? Get it in Treble! http://BlueTreble.com



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: pgaudit - an auditing extension for PostgreSQL
Next
From: Jim Nasby
Date:
Subject: Re: proposal: plpgsql - Assert statement