From: | Edson Richter <edsonrichter(at)hotmail(dot)com> |
---|---|
To: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Intermitent connection could corrupt slave database? |
Date: | 2015-04-10 19:51:58 |
Message-ID: | BLU436-SMTP112BEB195FB09DFACDAB62CFFA0@phx.gbl |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hi, folks!
I've a async master to slave database replication, both 9.3.5 running
Oracle Linux 7 x64.
Today, a intermitent link that ended with abrupt interruption, and made
necessary to promote the slave database to master.
After promotion, two medium databases (<5Gb) became active without
issues, and two of our biggest databases (around 60Gb) became corrupt
with error "... read only 0 of 8192" (the already known error). The
original databases are protected - besides not yet available due link
issues, so I'm on the "safe side".
But I'm curious if this "intermitent link" scenario is already covered
(perhaps in later releases), or this is something we cannot foresee/deal
with?
--
Atenciosamente,
Edson Carlos Ericksson Richter
From | Date | Subject | |
---|---|---|---|
Next Message | Volkan Unsal | 2015-04-10 20:06:49 | Re: no pg_hba.conf entry for replication connection from host |
Previous Message | Adrian Klaver | 2015-04-10 19:51:36 | Re: no pg_hba.conf entry for replication connection from host |