Re: Bad planning data resulting in OOM killing of postgres

From: Karsten Hilbert <Karsten(dot)Hilbert(at)gmx(dot)net>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: Bad planning data resulting in OOM killing of postgres
Date: 2017-02-15 12:04:51
Message-ID: 20170215120451.mpyec2uzckubx335@hermes.hilbert.loc
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Karsten Hilbert 2017-02-15 12:11:25 Re: Bad planning data resulting in OOM killing of postgres
Previous Message Tom Lane 2017-02-15 06:35:33 Re: Get tables ending with numbers