public inbox for [email protected]  

help / color / mirror / Atom feed

From: Peter Eisentraut <[email protected]>
To: Bruce Momjian <[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: Sun, 26 Aug 2012 23:43:45 -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]>
	<[email protected]>

I'm a little bit worried about this whole discussion.  We have half a
dozen supposed experts working on a 10-line shell script to do WAL
archiving, and there is still

- disagreement
- uncertainty
- bugs

How is a normal user supposed to do this?

That aside, I disagree with the premise for this script.  It doesn't do
anything more than the typical inline examples we give.  The additional
error reporting could be considered useful, but cp is perfectly capable
of reporting these errors itself, and getting in the way of that just
loses information and introduces race conditions.  But if we are going
to provide a separate shell script, we should at least offer some
additional value, such as addressing the partial copy problem.  But I
think that's not very easy to do in portable shell.

I think what we should do is write a wrapper program in C that covers
all the bases, support all platforms, and supports a handful of the most
commonly used copy methods (cp, scp, etc. + compression).  Then everyone
can just use that and doesn't have to figure all these things out from
scratch every time.

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