Date: Wed, 3 Apr 2019 20:16:12 +0000 (UTC)
From: LEROY TENNISON <leroy_tennison@prodigy.net>
To: Pgsql-admin <pgsql-admin@lists.postgresql.org>
Message-ID: <1222332414.512321.1554322572303@mail.yahoo.com>
Subject: archive_command options?
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_512320_1996339066.1554322572302"
References: <1222332414.512321.1554322572303.ref@mail.yahoo.com>
Content-Length: 2197
Precedence: bulk

------=_Part_512320_1996339066.1554322572302
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Postgresql documentation lists the following as an archive command for log =
shipping:
archive_command =3D 'test ! -f /mnt/server/archivedir/%f && cp %p /mnt/serv=
er/archivedir/%f'
The problem is that it is very fragile.=C2=A0 If anything breaks the copy (=
either system failing, network issues) then log shipping stops because the =
file exists in some intermediate state.=C2=A0 The result is that logs build=
 up on the source system filling disk space.=C2=A0 I've had to deal with a =
few of these this week, in two cases the file system was 98% full.=C2=A0 Is=
 there a reason rsync isn't used?=C2=A0 It has the ability to restart inter=
rupted transfers.=C2=A0 I don't want to use it only to find out i got mysel=
f into another predicament.=C2=A0 Any other less-fragile options?=C2=A0 Tha=
nks for the help.
------=_Part_512320_1996339066.1554322572302
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<html><head></head><body><div class=3D"yahoo-style-wrap" style=3D"font-fami=
ly:Helvetica Neue, Helvetica, Arial, sans-serif;font-size:13px;"><div><span=
><div>Postgresql documentation lists the following as an archive command fo=
r log shipping:</div><div><br></div><div>archive_command =3D 'test ! -f /mn=
t/server/archivedir/%f &amp;&amp; cp %p /mnt/server/archivedir/%f'</div><di=
v><br></div><div>The problem is that it is very fragile.&nbsp; If anything =
breaks the copy (either system failing, network issues) then log shipping s=
tops because the file exists in some intermediate state.&nbsp; The result i=
s that logs build up on the source system filling disk space.&nbsp; I've ha=
d to deal with a few of these this week, in two cases the file system was 9=
8% full.&nbsp; Is there a reason rsync isn't used?&nbsp; It has the ability=
 to restart interrupted transfers.&nbsp; I don't want to use it only to fin=
d out i got myself into another predicament.&nbsp; Any other less-fragile o=
ptions?&nbsp; Thanks for the help.</div></span></div></div></body></html>
------=_Part_512320_1996339066.1554322572302--