Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1etIJe-0007Qe-CS for pgsql-admin@arkaria.postgresql.org; Tue, 06 Mar 2018 19:32:02 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1etIJc-0002rj-Nk for pgsql-admin@arkaria.postgresql.org; Tue, 06 Mar 2018 19:32:00 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1etIJc-0002ra-DN for pgsql-admin@lists.postgresql.org; Tue, 06 Mar 2018 19:32:00 +0000 Received: from mail.thelabyrinth.net ([45.56.70.56]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1etIJZ-0007ao-Q0 for pgsql-admin@lists.postgresql.org; Tue, 06 Mar 2018 19:31:59 +0000 Received: from Davids-iMac.local (unknown [173.169.74.224]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: dsteele) by mail.thelabyrinth.net (Postfix) with ESMTPSA id A7F5954683; Tue, 6 Mar 2018 19:31:56 +0000 (UTC) Subject: Re: Reliable WAL file shipping over unreliable network To: Stephen Frost , Rui DeSousa Cc: pgsql-admin@lists.postgresql.org References: <988AB20C-9FDE-4197-BF3F-C54D80C2ED78@elevated-dev.com> <20180302180911.GO2416@tamriel.snowman.net> <20180304150640.GR2416@tamriel.snowman.net> <3D9CC2FB-57E1-45B2-B5FC-1B214F5DB068@icloud.com> <20180305111521.GV2416@tamriel.snowman.net> <20180305150218.GY2416@tamriel.snowman.net> <15F9D550-9909-40B3-A384-417AFCD745DF@icloud.com> <20180306190004.GQ2416@tamriel.snowman.net> From: David Steele Message-ID: <68099b52-3909-07e3-04ea-b5ba600b1767@pgmasters.net> Date: Tue, 6 Mar 2018 14:31:55 -0500 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <20180306190004.GQ2416@tamriel.snowman.net> Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="ozkXnlOzkJoSXjMlnlasl3fdOWUOrRiEq" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --ozkXnlOzkJoSXjMlnlasl3fdOWUOrRiEq Content-Type: multipart/mixed; boundary="SchaA7aHsVUeaHLNGa1zlZeZqaTWvBrhV"; protected-headers="v1" From: David Steele To: Stephen Frost , Rui DeSousa Cc: pgsql-admin@lists.postgresql.org Message-ID: <68099b52-3909-07e3-04ea-b5ba600b1767@pgmasters.net> Subject: Re: Reliable WAL file shipping over unreliable network References: <988AB20C-9FDE-4197-BF3F-C54D80C2ED78@elevated-dev.com> <20180302180911.GO2416@tamriel.snowman.net> <20180304150640.GR2416@tamriel.snowman.net> <3D9CC2FB-57E1-45B2-B5FC-1B214F5DB068@icloud.com> <20180305111521.GV2416@tamriel.snowman.net> <20180305150218.GY2416@tamriel.snowman.net> <15F9D550-9909-40B3-A384-417AFCD745DF@icloud.com> <20180306190004.GQ2416@tamriel.snowman.net> In-Reply-To: <20180306190004.GQ2416@tamriel.snowman.net> --SchaA7aHsVUeaHLNGa1zlZeZqaTWvBrhV Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 3/6/18 2:00 PM, Stephen Frost wrote: >=20 > * Rui DeSousa (rui.desousa@icloud.com) wrote: >>> On Mar 5, 2018, at 10:02 AM, Stephen Frost wrote= : >>> It doesn=E2=80=99t- but please don't encourage partial solutions whic= h have ver clear issues. >> >> Then problem is there are no good base utilities that is useful with a= rchive_command; unless you=E2=80=99re writing directly to an NFS mount or= a tape library. Even Barman recommends rsync with the archive_command; = if you are unable to use pg_receivexlog solution. There are countless Po= stgres documentation out there that recommends use of rsync with the arch= ive_command. =20 >> >> Here a solution that will fsync() file on the other end. >=20 > 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. +1. I believe there's been talk of a pgcopy utility before but it never went anywhere. I think it would be worth it just to have a decent example in the docs. --=20 -David david@pgmasters.net --SchaA7aHsVUeaHLNGa1zlZeZqaTWvBrhV-- --ozkXnlOzkJoSXjMlnlasl3fdOWUOrRiEq Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIzBAEBCgAdFiEEDkRHqfbjxwCMp7jigDa4glDlIUAFAlqe7KsACgkQgDa4glDl IUD5dRAAhbm/KuD61tS/r7Xt+Rd/wTW92xu7D1NglUPIp1LvcYQ0g6uunOnSW9tw IAEkXea3u5mRPwC0Sjf9MIhqrFjeCyE0BBJs6uTzN2IcWp/sU8eJ4oQXJ4P/oeg5 4RTD42N1Eq90+TLPEkn4HWdx+py8aRRrjGCumqFaQJayuAUaFivykk7ExjZKLOEj scubMhafw5Tc+z3vftb6ChvkLYAX9MJvRFoLhwRhjtKayj55j64XD35lHiK4DO3S KLFWkIDTT/1qEbSsh7O9+G4NwiU+BBL2fJ6RVHrxxZ8UF/04Hz8Sv8jp9J66hUlK xzYKfU1+QWnap1gYlUTfXiiv4H1wwdViOdRxfPZkdw7/1xA/WCdfVWjGNSA9qb2S ESSGTKUFpUZI+QrYBRmMKsUh+N6IV1ThCoGtFDbN8ab/il7g1YIZfyb1EnbfZjD0 oMJ3/xev5ucKMoTUauJI5xa8Y+MOzflv2u8U0N3pJOQ+34K82q6sXtKbqDvk/Ikl MMTnIWRm/r6/qJw09jeGPrTg4garZyoZ1RNwXUcYZmrOADdntEqSD8GkDqFdFvXm JQrW+JJMPJ6ttYAWgbumdRlhAuGsxhM61tHwBPW1znCA2Zhmkfg16GEdysv0nuog 416gMXzEuum2UIzLSmD5X0OINs2UZB9VU6b0cxg1etEv2UjICAw= =8kf8 -----END PGP SIGNATURE----- --ozkXnlOzkJoSXjMlnlasl3fdOWUOrRiEq--