Search Postgresql Archives

Intermitent connection could corrupt slave database?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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



--
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux