* Erik Rijkers (e...@xs4all.nl) wrote:
> On Tue, February 4, 2014 18:56, Christian Kruse wrote:
> > On 04/02/14 17:41, Erik Rijkers wrote:
> >> 2014-02-04 10:34:25.376 CET 29133 LOG: server process (PID 29459) was
> >> terminated by signal 9: Killed
> >
> > Did you check if this was the OOM kille
"Erik Rijkers" writes:
> On Tue, February 4, 2014 18:56, Christian Kruse wrote:
>> Did you check if this was the OOM killer? Should be logged in dmesg.
> I would be surprised if it wasn't. (no access to that machine at the moment)
> How do we regard such crashes? It seems to me this was rather
On Tue, February 4, 2014 18:56, Christian Kruse wrote:
> Hi,
>
> On 04/02/14 17:41, Erik Rijkers wrote:
>
>> 2014-02-04 10:34:25.376 CET 29133 LOG: server process (PID 29459) was
>> terminated by signal 9: Killed
>
> Did you check if this was the OOM killer? Should be logged in dmesg.
>
I would
Hi,
On 04/02/14 17:41, Erik Rijkers wrote:
> 2014-02-04 10:34:25.376 CET 29133 LOG: server process (PID 29459) was
> terminated by signal 9: Killed
Did you check if this was the OOM killer? Should be logged in dmesg.
Best regards,
--
Christian Kruse http://www.2ndQuadrant.com
CentOS Release 6.5 (final)
AMD FX(tm)-8120 Eight-Core
2.6.32-431.3.1.el6.x86_64 #1 SMP Fri Jan 3 21:39:27 UTC 2014 x86_64 x86_64
x86_64 GNU/Linux
memory: 8GB
I am testing nested hstore, on a server with both with these patches:
jsonb-9.patch.gz
nested-hstore-9.patch.gz
One of the first tries