Re: Reliable WAL file shipping over unreliable network - Mailing list pgsql-admin

From Rui DeSousa
Subject Re: Reliable WAL file shipping over unreliable network
Date
Msg-id 3D9CC2FB-57E1-45B2-B5FC-1B214F5DB068@icloud.com
Whole thread Raw
In response to Re: Reliable WAL file shipping over unreliable network  (Stephen Frost <sfrost@snowman.net>)
Responses Re: Reliable WAL file shipping over unreliable network  (Stephen Frost <sfrost@snowman.net>)
List pgsql-admin
In that case I suggest reading up on replication slots and pg_receievexlog.  Everyone’s tropology and requirements are
differentand there are many ways to skin a cat.  

> On Mar 4, 2018, at 10:06 AM, Stephen Frost <sfrost@snowman.net> wrote:
>
> Greetings,
>
> * Rui DeSousa (rui.desousa@icloud.com) wrote:
>> Not a problem; as you should be archiving your WALs to multiple sites simultaneously.  You’re DR site should not
relyon 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



pgsql-admin by date:

Previous
From: Mike Lonergan
Date:
Subject: Re: What is the accepted practice to automate initdb (PostgreSQL 9.6)to a non-default directory?
Next
From: Laurenz Albe
Date:
Subject: Re: Finding out the aging tables for vacuuming to prevent data losson transaction id wraparound