From: | Rui DeSousa <rui(dot)desousa(at)icloud(dot)com> |
---|---|
To: | Stephen Frost <sfrost(at)snowman(dot)net> |
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 22:29:44 |
Message-ID: | 3D9CC2FB-57E1-45B2-B5FC-1B214F5DB068@icloud.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
In that case I suggest reading up on replication slots and pg_receievexlog. Everyone’s tropology and requirements are different and there are many ways to skin a cat.
> On Mar 4, 2018, at 10:06 AM, Stephen Frost <sfrost(at)snowman(dot)net> wrote:
>
> 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 | Laurenz Albe | 2018-03-05 09:24:22 | Re: Finding out the aging tables for vacuuming to prevent data loss on transaction id wraparound |
Previous 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? |