| From: | Rui DeSousa <rui(dot)desousa(at)icloud(dot)com> |
|---|---|
| To: | scott ribe <scott_ribe(at)elevated-dev(dot)com> |
| Cc: | Nagy László Zsolt <gandalf(at)shopzeus(dot)com>, pgsql-admin(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Reliable WAL file shipping over unreliable network |
| Date: | 2018-02-28 18:15:48 |
| Message-ID: | 37C5A42B-4CDD-4F01-8F1E-1B185C1819B9@icloud.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Sure it does… what happens if the archive server gets full? There is a situation that can fool rsync into thinking it was successfully transferred as rsync only relies on filesystem metadata to verify the file is different. The “-c” option will validate the file using a checksum and not just rely on just filesystem metadata.
Trust me on this one; I’ve seen this happen.
> On Feb 28, 2018, at 1:05 PM, scott ribe <scott_ribe(at)elevated-dev(dot)com> wrote:
>
> On Feb 28, 2018, at 10:05 AM, Rui DeSousa <rui(dot)desousa(at)icloud(dot)com> wrote:
>>
>> Just use "-ac”; you want -c option to ensure no data corruption during the transfer. Do not delete the file; let Postgres manage that.
>
> -c has nothing to do with data corruption during transfer
>
> --
> Scott Ribe
> https://www.linkedin.com/in/scottribe/
> (303) 722-0567
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Evan Rempel | 2018-02-28 18:17:14 | Re: Separate log for a specfic database |
| Previous Message | scott ribe | 2018-02-28 18:12:03 | Re: Reliable WAL file shipping over unreliable network |