public inbox for [email protected]  
help / color / mirror / Atom feed
From: Bruce Momjian <[email protected]>
To: Peter Eisentraut <[email protected]>
Cc: Josh Kupershmidt <[email protected]>
Cc: Greg Smith <[email protected]>
Cc: Euler Taveira de Oliveira <[email protected]>
Cc: [email protected]
Subject: Re: somewhat wrong archive_command example
Date: Sat, 25 Aug 2012 19:40:26 -0400
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<CAK3UJRHChOcGQ0kzu01wZX6PB9pScHSzg1X+hThdR7QXWoe1yw@mail.gmail.com>
	<[email protected]>
	<[email protected]>
	<[email protected]>

On Sat, Aug 25, 2012 at 07:07:55PM -0400, Bruce Momjian wrote:
> > >I have made all the suggestions posted and would like to add the
> > >attached script to our documentation as a simple example.
> > 
> > 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 have occasionally used some combination of mktemp + cp + mv, which
> > seems to work around this problem.
> 
> I am unclear why the script returns success if the file already exists
> --- seems if the file exists, we should throw an error, like we have
> always done with cp -i < /dev/null.
> 
> Updated version attached.
> 
> Another option in this case would be to re-issue the copy.

Sorry, proper attached file this time.

-- 
  Bruce Momjian  <[email protected]>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

  + It's impossible for everything to be true. +


Attachments:

  [application/x-sh] local_backup_script.sh (555B, 2-local_backup_script.sh)
  download

view thread (24+ messages)  latest in thread

reply

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: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected], [email protected]
  Subject: Re: somewhat wrong archive_command example
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox