Re: Critical failure of standby - Mailing list pgsql-general

From John R Pierce
Subject Re: Critical failure of standby
Date
Msg-id 5892028d-612d-335b-6cc1-5ddcf8a2cce0@hogranch.com
Whole thread Raw
In response to Re: Critical failure of standby  (James Sewell <james.sewell@jirotech.com>)
Responses Re: Critical failure of standby  (James Sewell <james.sewell@jirotech.com>)
List pgsql-general
On 8/15/2016 7:23 PM, James Sewell wrote:
> Those are all good questions.
>
> Essentially this is a situation where DR is network separated from
> Prod - so I would expect the archive command to fail. I'll have to
> check the script it must not be passing the error back through to
> PostgreSQL.
>
> This still shouldn't cause database corruption though right? - it's
> just not getting WALs.

if the slave database is asking for the WAL's, it needs them. if it
needs them and can't get them, then it can't catch up and start.



--
john r pierce, recycling bits in santa cruz



pgsql-general by date:

Previous
From: James Sewell
Date:
Subject: Re: Critical failure of standby
Next
From: Adam Brusselback
Date:
Subject: Re: C++ port of Postgres