Re: problem with archive_command as suggested by documentation - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: problem with archive_command as suggested by documentation
Date
Msg-id 497DA755.8060807@gmx.net
Whole thread Raw
In response to Re: problem with archive_command as suggested by documentation  (Simon Riggs <simon@2ndQuadrant.com>)
List pgsql-hackers
Simon Riggs wrote:
> I don't think that particular example is a good one since the whole
> point of the archive is that it should be off-server. If we're going to
> be exact about the example then we should give a more realistic one,
> like using scp. Unfortunately, there is no secure-remote-move command,
> so doing the above with scp would resend the whole file 3 times. I think
> it's better to write a script...

The problem is that most people do copy the stuff straight out of the 
documentation.  And for those that do write a separate script, there are 
still a lot of possibilities to get it wrong.

There are only about a handful of transportation protocols appearing in 
practice, so it would be very helpful to provide carefully reviewed 
scripts or recipes for these.


pgsql-hackers by date:

Previous
From: Dave Page
Date:
Subject: Re: 8.4 release planning (was Re: [COMMITTERS] pgsql: Automatic view update rules)
Next
From: Peter Eisentraut
Date:
Subject: Re: [PATCH] reloptions - RELOPT_KIND_ALL