| From: | Nagy László Zsolt <gandalf(at)shopzeus(dot)com> |
|---|---|
| To: | 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-02-28 19:11:33 |
| Message-ID: | 10bea809-cf89-4e5d-6064-95dd95164e20@shopzeus.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
2018. 02. 28. 19:11 keltezéssel, Rui DeSousa írta:
> Easiest thing to do is to keep the replica from seeing the file until
> it’s successfully transferred; i.e.
>
> 1. Transfer the file successfully first with a temporary extension:
> $ARCH_DIR/$WALFILE.swap
> 2. If successfully transferred then move it into place:
> mv $ARCH_DIR/$WALFILE.swap $ARCH_DIR/$WALFILE
This works ONLY if the directory is mounted on the master, and you can
execute "mv" on the master (as part of the archive_command) to rename
the file that is stored on the slave.
But the original question specified that mounting is not an option.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rui DeSousa | 2018-02-28 19:12:39 | Re: Reliable WAL file shipping over unreliable network |
| Previous Message | scott ribe | 2018-02-28 19:11:15 | Re: Reliable WAL file shipping over unreliable network |