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
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
