| From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
|---|---|
| To: | Stephen Frost <sfrost(at)snowman(dot)net>, Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, Andres Freund <andres(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Josh Berkus <josh(at)agliodbs(dot)com> |
| Subject: | Re: pg_upgrade and rsync |
| Date: | 2015-01-27 23:09:00 |
| Message-ID: | 54C81A8C.8030705@BlueTreble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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 to the 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim Nasby | 2015-01-27 23:13:29 | Re: proposal: plpgsql - Assert statement |
| Previous Message | Robert Haas | 2015-01-27 23:06:36 | Re: pgaudit - an auditing extension for PostgreSQL |