Postgres Pro
Downloads
Home   >   mailing lists

Re: [GENERAL] Bad planning data resulting in OOM killing of postgres - Mailing list pgsql-general

From Karsten Hilbert
Subject Re: [GENERAL] Bad planning data resulting in OOM killing of postgres
Date
Msg-id 20170215120451.mpyec2uzckubx335@hermes.hilbert.loc
Whole thread Raw
In response to Re: [GENERAL] Bad planning data resulting in OOM killing of postgres  (David Hinkle <hinkle@cipafilter.com>)
Responses Re: [GENERAL] Bad planning data resulting in OOM killing of postgres  (Karsten Hilbert <Karsten.Hilbert@gmx.net>)
List pgsql-general
Tree view 
On Mon, Feb 13, 2017 at 03:47:08PM -0600, David Hinkle wrote:


> Nope, that pops too.  The query runs for a long time at a somewhat
> normal rate of ram consumption, using ~1G of RSS then suddenly spikes
> to about 6G, at which point the OOM killer pops it.  Box has 8G of ram
> and 4G of swap.

By any chance:

- when it happens has the kernel considered using swap ?

- which kernel are you running ?

There's been (for some workloads) massive problems with RAM
exhaustion / swapping / OOM killer going wild with
4.7/4.8/some 4.9 kernels.

Just a shot in the dark,
Karsten
--
GPG key ID E4071346 @ eu.pool.sks-keyservers.net
E167 67FD A291 2BEA 73BD  4537 78B9 A9F9 E407 1346

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: [GENERAL] Get tables ending with numbers
Next
From: Karsten Hilbert
Date:
Subject: Re: [GENERAL] Bad planning data resulting in OOM killing of postgres