pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: David Steele <david@pgmasters.net>
To: Rui DeSousa <rui.desousa@icloud.com>
To: Stephen Frost <sfrost@snowman.net>
Cc: pgsql-admin@lists.postgresql.org
Subject: Re: Reliable WAL file shipping over unreliable network
Date: Tue, 6 Mar 2018 13:47:35 -0500
Message-ID: <b01c51be-2f5d-a158-7e8b-be39b5e99162@pgmasters.net> (raw)
In-Reply-To: <15F9D550-9909-40B3-A384-417AFCD745DF@icloud.com>
References: <6056907B-551F-4ED0-804B-0FCACD39EB23@icloud.com>
	<ea674584-85bc-3f63-c182-0d45123bb3eb@catalyst.net.nz>
	<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>

On 3/6/18 12:55 PM, Rui DeSousa wrote:
> 
>> On Mar 5, 2018, at 10:02 AM, Stephen Frost <sfrost@snowman.net
>> <mailto:sfrost@snowman.net>> wrote:
>>
>> It doesn’t- but please don't encourage partial solutions which have
>> ver clear issues.
> 
> Then problem is there are no good base utilities that is useful with
> archive_command; unless you’re writing directly to an NFS mount or a
> tape library.  

It's true that there are no good base utilities for this purpose, not
sure why NFS would be an exception, though.

> Even Barman recommends rsync with the archive_command; if
> you are unable to use pg_receivexlog solution.  There are
> countless Postgres documentation out there that recommends use of rsync
> with the archive_command.  

Also true, even though rsync has show itself to be a poor tool for
database backups.

> Here a solution that will fsync() file on the other end.
At a quick glance, that looks like it would work.

But why go through the trouble when pgBackRest does all of that (and
much more), and does not rely on rsync?  You are obviously knowledgeable
and like to do it yourself, but not everybody wants to develop a
solution from scratch, test it, and maintain it.

Regards,
-- 
-David
david@pgmasters.net




view thread (59+ messages)  latest in thread

Message-ID: <b01c51be-2f5d-a158-7e8b-be39b5e99162@pgmasters.net>
Permalink:  ../b01c51be-2f5d-a158-7e8b-be39b5e99162@pgmasters.net/
Also on:    postgresql.org/message-id/b01c51be-2f5d-a158-7e8b-be39b5e99162@pgmasters.net

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: david@pgmasters.net, rui.desousa@icloud.com, sfrost@snowman.net, pgsql-admin@lists.postgresql.org
  Subject: Re: Reliable WAL file shipping over unreliable network
  In-Reply-To: <b01c51be-2f5d-a158-7e8b-be39b5e99162@pgmasters.net>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox