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

From Albe Laurenz
Subject Re: problem with archive_command as suggested by documentation
Date
Msg-id D960CB61B694CF459DCFB4B0128514C22D6E97@exadv11.host.magwien.gv.at
Whole thread Raw
In response to problem with archive_command as suggested by documentation  ("Albe Laurenz" <laurenz.albe@wien.gv.at>)
Responses Re: problem with archive_command as suggested by documentation  (David Fetter <david@fetter.org>)
List pgsql-hackers
Peter Eisentraut 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.

I'll try to come up with something, but it will take some time; an impending
addition to the family currently has priority...

Yours,
Laurenz Albe


pgsql-hackers by date:

Previous
From: Gregory Stark
Date:
Subject: Re: 8.4 release planning
Next
From: Tom Lane
Date:
Subject: Re: 8.4 release planning