| From: | scott ribe <scott_ribe(at)elevated-dev(dot)com> |
|---|---|
| To: | Nagy László Zsolt <gandalf(at)shopzeus(dot)com> |
| Cc: | pgsql-admin(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Reliable WAL file shipping over unreliable network |
| Date: | 2018-02-28 16:38:57 |
| Message-ID: | BA4A1866-95B0-49C6-8CD1-3D1B60A7837E@elevated-dev.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Feb 28, 2018, at 8:46 AM, Nagy László Zsolt <gandalf(at)shopzeus(dot)com> wrote:
>
> Another problem with rsync might be that it does not know if a WAL file
> on the source side is growing (e.g. being written) and it might start
> copy that before it is fully flushed to disk. I see this as a big
> problem, but I don't have experience.
You use rsync in the archive command, not by itself. Postgres does not try to copy the file until it is ready.
> E.g. move the file into the archive dir only after it has been fully
> copied to the destination volume. But then we still have the problem of
> partially written files on the slave side.
No, you do not have that problem at all.
Given an unreliable network, you probably do want to use --partial
--
Scott Ribe
https://www.linkedin.com/in/scottribe/
(303) 722-0567
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jimmy Augustine | 2018-02-28 16:59:31 | Re: PostgreSQL 9.6 Temporary files |
| Previous Message | Nagy László Zsolt | 2018-02-28 15:46:42 | Re: Reliable WAL file shipping over unreliable network |