Re: pg killed by oom-killer, "invalid contrecord length 2190 at A6C/331AAA90" on slaves

I'm no PG expert but it seem that your WAL record is corrupt just on
this one slave.
Perhaps you can check this with md5 or something.

perhaps your master process die in this moment there the file was written?
So the question is
"How does PG sync WAL file between multiple slaves?"
Async or Synchronous?

Am 27.10.2014 17:00, schrieb Joe Van Dyk:
>
> On Mon, Oct 27, 2014 at 8:16 AM, basti <mailinglist(at)unix-solution(dot)de
> <mailto:mailinglist(at)unix-solution(dot)de>> wrote:
>
> 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
>
>
> Thanks -- my question is not so much about the oom killer, but rather
> about why just one of the slaves is reporting the "invalid contrecord
> length" error.
>
>
> I hope that's helpful.
>
> Regards,
> basti
>
> On Sat 25.10.2014 22:55 +0200, Joe Van Dyk <joe(at)tanga(dot)com
> <mailto:joe(at)tanga(dot)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
>
>
> --
> Sent via pgsql-general mailing list (pgsql-general(at)postgresql(dot)org
> <mailto:pgsql-general(at)postgresql(dot)org>)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general
>
>