From: | Stephen Frost <sfrost(at)snowman(dot)net> |
---|---|
To: | Rui DeSousa <rui(dot)desousa(at)icloud(dot)com> |
Cc: | scott ribe <scott_ribe(at)elevated-dev(dot)com>, Mark Kirkwood <mark(dot)kirkwood(at)catalyst(dot)net(dot)nz>, Dianne Skoll <dfs(at)roaringpenguin(dot)com>, pgsql-admin(at)lists(dot)postgresql(dot)org |
Subject: | Re: Reliable WAL file shipping over unreliable network |
Date: | 2018-03-04 15:06:40 |
Message-ID: | 20180304150640.GR2416@tamriel.snowman.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Greetings,
* Rui DeSousa (rui(dot)desousa(at)icloud(dot)com) wrote:
> Not a problem; as you should be archiving your WALs to multiple sites simultaneously. You’re DR site should not rely on any resources stored at the primary site.
Please don't top-post on the PG mailing lists. We prefer in-line
responses, such as this.
I agree that archiving WAL to multiple sites is a good idea, but none of
the proposed examples does that or even provides a way to easily and
reliably do it, so that doesn't actually address the issue.
Thanks!
Stephen
From | Date | Subject | |
---|---|---|---|
Next Message | Mike Lonergan | 2018-03-04 17:25:41 | Re: What is the accepted practice to automate initdb (PostgreSQL 9.6) to a non-default directory? |
Previous Message | Mike Lonergan | 2018-03-03 00:18:41 | Re: What is the accepted practice to automate initdb (PostgreSQL 9.6) to a non-default directory? |