From: Steve Crawford <scrawford@pinpointresearch.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: David.Bear@asu.edu
Cc: pgsql-admin@postgresql.org
Subject: Re: PITR with rsync
Date: Tue, 07 Aug 2007 08:37:02 -0700
Message-ID: <46B8919E.7030408@pinpointresearch.com> (raw)
In-Reply-To: <6080.1186448021@sss.pgh.pa.us>
References: <20070807001114.GD19294@asu.edu>
<5382.1186446433@sss.pgh.pa.us>
<20070807004608.GE19294@asu.edu>
<6080.1186448021@sss.pgh.pa.us>
> 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...
Actually, rsync has one edge over scp even where its other attributes
are moot: atomicity.
Rsync keeps the data in a temporary location then moves the whole file
into place at the conclusion of a successful transfer. Scp, however,
creates the file at start of transfer and that file will continue to
grow as the transfer progresses. A failure part-way through a scp
transfer will leave an incomplete file on the receiving end.
For situations where a process on the receiving side watches for and
processes newly added files or situations where I require a reliable
all-or-none transfer such as distribution of configuration files, I use
rsync.
Of course this attribute of rsync means that updates of an existing file
require sufficient disk-space for both old and new versions of the file.
Cheers,
Steve
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: scrawford@pinpointresearch.com, tgl@sss.pgh.pa.us, David.Bear@asu.edu
Subject: Re: PITR with rsync
In-Reply-To: <46B8919E.7030408@pinpointresearch.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