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 wrote:
> One of my postgres backends was killed
On Tue, Oct 28, 2014 at 7:43 AM, Andres Freund
wrote:
> On 2014-10-25 13:55:57 -0700, Joe Van Dyk 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
On 2014-10-25 13:55:57 -0700, Joe Van Dyk 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 sla
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 slave
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 Synchro
On Mon, Oct 27, 2014 at 8:16 AM, basti 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
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 wrote:
> One of my postgres backends was killed
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
