Received: from localhost (maia-1.hub.org [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id 829019FB82B for ; Tue, 7 Aug 2007 12:37:13 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.191]) (amavisd-maia, port 10024) with ESMTP id 10616-01-4 for ; Tue, 7 Aug 2007 12:37:04 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from polaris.pinpointresearch.com (66-7-238-130.static-ip.telepacific.net [66.7.238.130]) by postgresql.org (Postfix) with ESMTP id 0F55D9FBC6A for ; Tue, 7 Aug 2007 12:37:04 -0300 (ADT) Received: from [192.168.1.179] (betelgeuse.pinpointresearch.com [192.168.1.179]) by polaris.pinpointresearch.com (Postfix) with ESMTP id CA8E2E00EC82; Tue, 7 Aug 2007 08:37:02 -0700 (PDT) Message-ID: <46B8919E.7030408@pinpointresearch.com> Date: Tue, 07 Aug 2007 08:37:02 -0700 From: Steve Crawford User-Agent: Thunderbird 1.5.0.10 (X11/20060911) MIME-Version: 1.0 To: Tom Lane CC: David.Bear@asu.edu, pgsql-admin@postgresql.org Subject: Re: PITR with rsync References: <20070807001114.GD19294@asu.edu> <5382.1186446433@sss.pgh.pa.us> <20070807004608.GE19294@asu.edu> <6080.1186448021@sss.pgh.pa.us> In-Reply-To: <6080.1186448021@sss.pgh.pa.us> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200708/46 X-Sequence-Number: 26377 > 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