From: | David Steele <david(at)pgmasters(dot)net> |
---|---|
To: | Stephen Frost <sfrost(at)snowman(dot)net>, Rui DeSousa <rui(dot)desousa(at)icloud(dot)com> |
Cc: | pgsql-admin(at)lists(dot)postgresql(dot)org |
Subject: | Re: Reliable WAL file shipping over unreliable network |
Date: | 2018-03-06 19:31:55 |
Message-ID: | 68099b52-3909-07e3-04ea-b5ba600b1767@pgmasters.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On 3/6/18 2:00 PM, Stephen Frost wrote:
>
> * Rui DeSousa (rui(dot)desousa(at)icloud(dot)com) wrote:
>>> On Mar 5, 2018, at 10:02 AM, Stephen Frost <sfrost(at)snowman(dot)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. 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.
>>
>> 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.
+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.
--
-David
david(at)pgmasters(dot)net
From | Date | Subject | |
---|---|---|---|
Next Message | Johannes Truschnigg | 2018-03-06 19:39:33 | Re: Reliable WAL file shipping over unreliable network |
Previous Message | Stephen Frost | 2018-03-06 19:00:04 | Re: Reliable WAL file shipping over unreliable network |