Date: Tue, 6 Mar 2018 14:00:04 -0500
From: Stephen Frost <sfrost@snowman.net>
To: Rui DeSousa <rui.desousa@icloud.com>
Cc: pgsql-admin@lists.postgresql.org
Subject: Re: Reliable WAL file shipping over unreliable network
Message-ID: <20180306190004.GQ2416@tamriel.snowman.net>
References: <988AB20C-9FDE-4197-BF3F-C54D80C2ED78@elevated-dev.com>
 <E6AB850C-D05E-405B-8D4E-DE18E128F402@icloud.com>
 <20180302180911.GO2416@tamriel.snowman.net>
 <BB8E0E71-D65F-409F-B9AD-DDF2237CDF99@icloud.com>
 <20180304150640.GR2416@tamriel.snowman.net>
 <3D9CC2FB-57E1-45B2-B5FC-1B214F5DB068@icloud.com>
 <20180305111521.GV2416@tamriel.snowman.net>
 <ABC9F093-7249-498E-901B-6ADB7BBA3B22@icloud.com>
 <20180305150218.GY2416@tamriel.snowman.net>
 <15F9D550-9909-40B3-A384-417AFCD745DF@icloud.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512;
	protocol="application/pgp-signature"; boundary="TeC/WBK0AnoA6gv8"
Content-Disposition: inline
In-Reply-To: <15F9D550-9909-40B3-A384-417AFCD745DF@icloud.com>
User-Agent: Mutt/1.5.24 (2015-08-30)
Precedence: bulk


--TeC/WBK0AnoA6gv8
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Greetings,

* Rui DeSousa (rui.desousa@icloud.com) wrote:
> > On Mar 5, 2018, at 10:02 AM, Stephen Frost <sfrost@snowman.net> wrote:
> > It doesn=E2=80=99t- but please don't encourage partial solutions which =
have ver clear issues.
>=20
> Then problem is there are no good base utilities that is useful with arch=
ive_command; unless you=E2=80=99re writing directly to an NFS mount or a ta=
pe library.  Even Barman recommends rsync with the archive_command; if you =
are unable to use pg_receivexlog solution.  There are countless Postgres do=
cumentation out there that recommends use of rsync with the archive_command=
=2E =20
>=20
> Here a solution that will fsync() file on the other end.

I'd encourage you to consider submitting this to a commitfest to get
feedback on it, as a proper patch to add such a utlity to PG and which
we could use in our documentation instead of saying "cp", which is
pretty terrible.

Then again, as David mentioned, there are already utilities which do
this properly, even if they're not included in core today.

Thanks!

Stephen

--TeC/WBK0AnoA6gv8
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBCgAGBQJanuU0AAoJEO1sijiDR2RViYgP/RLwQ+FG3WpBiVW5kWpXYdJ+
YKVW9kfOhData9djZmEugmZHX3+tgNpn1Pyteb5nl15y4kqe926JNFfgnj2Nt/xa
M2NnaHSeTAv2Cl2XgL3pY9i5qzIqccizzsGZ/2vMsV3TNxJEHe0Q1vgVWHZC+y/M
juyC3Dnv+JmXDGfjP7977cQwnTFhnC4mDB3MUW+f7tquynRrD6dEejQ9aJIWL9lT
OgYGe95xf22LGnYd0rxf4OTgf3OGxjAf2ZknpCKnLIoLAKr4zaHmvgA9ImQwEvAj
afT1d4BV9W9yK+fC2wseeF9OPz8OVBzTd9TXGq2b5iTicILfm3vIr50bnZJV/QYD
Bl6XIQkKt24X6HvfQ2wcrTMx8FMdhjlrX+XX0TLlbSe80BQ+lKHTurb4sUZLfpPq
lH7JBFNOvKQhynh/iU8A19JfYTPn1dhLK3pYt8D7eIg8NHgK7MJNk8eJLTyZTgV0
ttLnVGXguzhq+jVoDzYhnEDLFqLeXJ/rFT9DdIEzX0JwAh3G3b+oI1y0n1HDbLSn
NvC3W8Y64s+V4ATwPGpNutdmV3x7mkD4RCd8CHEB1XwCFgddW/Y2+ZRnuK3CcCW8
C3NDrgAG0K1p5Pv3iLfVd/xSDkKFt6wuajndERKFSCTbHnvKLSmP7wj+JkeG2jwA
ThiAJ9OkxaK0Zgg3pX+I
=AGYo
-----END PGP SIGNATURE-----

--TeC/WBK0AnoA6gv8--