El 25/10/14 a las 17:55, Joe Van Dyk escibió: > One of my postgres backends was killed by the oom-killer. Now, one of > my streaming replication slaves is reporting "invalid contrecord > length 2190 at A6C/331AAA90" in the logs and replication has paused. I > have other streaming replication slaves that are fine. > > Is that expected? It's happened twice in two days. > > I'm running 9.3.5 on the master. I have 9.3.4 on the slave that has > the problem, and 9.3.5 on the slave that doesn't have the problem. Is > this something that was fixed in 9.3.5? > > The slave that has the problem is also located across the country, > while the slave that works is in the same data center as the master -- > not sure if that's related at all. > > Joe It's a corrupted slave. You'll need to regenerate it to ensure that your data is safe. The OOM killer doesn't respect what it kills, so this certain things can happen without a proper kernel configuration. -- -- Emanuel Calvo http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
