Re: pg killed by oom-killer, "invalid contrecord length 2190 at A6C/331AAA90" on slaves
От | basti |
---|---|
Тема | Re: pg killed by oom-killer, "invalid contrecord length 2190 at A6C/331AAA90" on slaves |
Дата | |
Msg-id | 544E61D5.8000401@unix-solution.de обсуждение исходный текст |
Ответ на | pg killed by oom-killer, "invalid contrecord length 2190 at A6C/331AAA90" on slaves (Joe Van Dyk <joe@tanga.com>) |
Ответы |
Re: pg killed by oom-killer, "invalid contrecord length
2190 at A6C/331AAA90" on slaves
|
Список | pgsql-general |
Hello, months ago I have a similar problem with the OOM-Killer. Have a look at http://www.credativ.co.uk/credativ-blog/2010/03/postgresql-and-linux-memory-management I hope that's helpful. Regards, basti On Sat 25.10.2014 22:55 +0200, Joe Van Dyk <joe@tanga.com> wrote: > 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
В списке pgsql-general по дате отправления: