On 3/6/18 12:55 PM, Rui DeSousa wrote: > >> On Mar 5, 2018, at 10:02 AM, Stephen Frost <sfrost@xxxxxxxxxxx >> <mailto:sfrost@xxxxxxxxxxx>> 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@xxxxxxxxxxxxx
