From: Greg Sabino Mullane <greg@turnstep.com>
To: pgsql-admin@postgresql.org
Subject: Re: PITR with rsync
Date: Tue, 7 Aug 2007 16:35:54 -0000
Message-ID: <6741ad8e3e180ae26294a16502c8221b@biglumber.com> (raw)
In-Reply-To: <6080.1186448021@sss.pgh.pa.us>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160
Tom Lane wrote:
>> well, I was using rysnc so I could copy to a different computer over
>> ssh, not using the rsync protocol to catch diffs. I don't have a
>> remote file system mounted so I can do just a cp.
> If you are going over an ssh connection then scp seems like the
> appropriate tool. Yeah, rsync would work, but it's just a useless
> extra layer of software...
In addition to the atomicity advantage, rsync allows compression of the
data on the fly. While you can also pass the -C flag to scp, I've found
that the high compressibility of WAL files means that rsync -z is noticeably
faster than scp -C (not that I would use the latter due to the partial file
issue).
- --
Greg Sabino Mullane greg@turnstep.com
End Point Corporation
PGP Key: 0x14964AC8 200708071229
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-----BEGIN PGP SIGNATURE-----
iD8DBQFGuJ6FvJuQZxSWSsgRA9xdAKDL4VZONTcmuXJl7Cz4bqiWXWVuZQCfRJso
2QIy8xDl88G4AnMFNrADVhM=
=iuKm
-----END PGP SIGNATURE-----
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: greg@turnstep.com
Subject: Re: PITR with rsync
In-Reply-To: <6741ad8e3e180ae26294a16502c8221b@biglumber.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox