Message-ID: <502EA9C2.2030100@timbira.com>
Date: Fri, 17 Aug 2012 17:29:54 -0300
From: Euler Taveira <euler@timbira.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
	rv:10.0.5) Gecko/20120624 Icedove/10.0.5
MIME-Version: 1.0
To: Peter Eisentraut <peter_e@gmx.net>
CC: Bruce Momjian <bruce@momjian.us>, Josh Kupershmidt <schmiddy@gmail.com>,
	Greg Smith <greg@2ndquadrant.com>, pgsql-docs@postgresql.org
Subject: Re: somewhat wrong archive_command example
References: <1316524671.9044.12.camel@fsopti579.F-Secure.com>
	<4E794FB5.80400@2ndQuadrant.com>
	<1316613536.14119.6.camel@fsopti579.F-Secure.com>
	<4E7A6D0D.4060106@2ndQuadrant.com> <4E7A887F.8010908@timbira.com>
	<CAK3UJRHChOcGQ0kzu01wZX6PB9pScHSzg1X+hThdR7QXWoe1yw@mail.gmail.com>
	<20120816011347.GF8353@momjian.us> <502EA0D0.10004@gmx.net>
In-Reply-To: <502EA0D0.10004@gmx.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

On 17-08-2012 16:51, Peter Eisentraut wrote:
> Btw., is anyone else concerned about using plain cp for this?  If the cp fails
> half-way, it leaves a partial file around, but subsequent file existence
> checks will find the file OK and skip it.
> 
I've already faced this problem (with cp and scp).

> I have occasionally used some combination of mktemp + cp + mv, which seems to
> work around this problem.
> 
That's what rsync uses, no? Your suggestion or rsync seem safe options to me.
But if you insist on an academic example using cp, at least comment that it
can fail in some cases.


-- 
   Euler Taveira de Oliveira - Timbira       http://www.timbira.com.br/
   PostgreSQL: Consultoria, Desenvolvimento, Suporte 24x7 e Treinamento