| From: | Joe Van Dyk <joe(at)tanga(dot)com> |
|---|---|
| To: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | pg killed by oom-killer, "invalid contrecord length 2190 at A6C/331AAA90" on slaves |
| Date: | 2014-10-25 20:55:57 |
| Message-ID: | CACfv+pLR8pDqyb1YYUu7MYZ6Fb_iZW6Rw2L+9b5+70JPoDPc6A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Francisco Olarte | 2014-10-26 07:50:40 | Re: Non-capturing expressions |
| Previous Message | Joe Van Dyk | 2014-10-25 20:29:25 | Re: Finding date intersections |