From: | Stephen Frost <sfrost(at)snowman(dot)net> |
---|---|
To: | Christoph Moench-Tegeder <cmt(at)burggraben(dot)net> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Logging the fact that a log was shipped |
Date: | 2017-08-28 17:28:44 |
Message-ID: | 20170828172844.GS4628@tamriel.snowman.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
* Christoph Moench-Tegeder (cmt(at)burggraben(dot)net) wrote:
> ## Stephen Frost (sfrost(at)snowman(dot)net):
>
> > Worse, such scripts run the serious risk of losing WAL if a crash
> > happens because nothing is ensuring that the WAL has been sync'd to disk
> > before returning from the archive_command.
>
> That risk already exists when using rsync/scp/scp/... and should be
> mitigated by filesystem settings on the receiving side.
I was including rsync/scp/similar based tools, yes, just pointing out
that such tools should be avoided when doing PG backups and WAL
archiving.
I have a hard time seeing "require filesystems be mounted as sync" to
really be a viable solution, though I suppose it would be technically
correct.
Thanks!
Stephen
From | Date | Subject | |
---|---|---|---|
Next Message | Gabriel Furstenheim Milerud | 2017-08-28 19:04:10 | Re: Extension coverage |
Previous Message | Christoph Moench-Tegeder | 2017-08-28 15:11:40 | Re: Logging the fact that a log was shipped |