Subject: Re: OOM Killing on Docker while ANALYZE running
To: pgsql-admin@lists.postgresql.org
References: <20180125194720.ammwkya3dvj23rjc@alvherre.pgsql>
 <29102.1516913306@sss.pgh.pa.us>
 <4e519ceb-d4ff-1cbf-1536-a96a79426ea2@vt.edu>
From: Mark Kirkwood <mark.kirkwood@catalyst.net.nz>
Message-ID: <41aac336-d5ed-9cf2-15d8-cf3783b7fea5@catalyst.net.nz>
Date: Fri, 26 Jan 2018 17:15:39 +1300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101
 Thunderbird/52.5.0
MIME-Version: 1.0
In-Reply-To: <4e519ceb-d4ff-1cbf-1536-a96a79426ea2@vt.edu>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Precedence: bulk

On 26/01/18 15:51, Ray Stell wrote:

> On 1/25/18 3:48 PM, Tom Lane wrote:
>
>> Alvaro Herrera <alvherre@alvh.no-ip.org> writes:
>>> Jorge Daniel wrote:
>>>> Hi guys , I'm dealing with OOM killing on Postgresql 9.4.8 running 
>>>> on docker
>
> Mike Coleman's talk at DockerCon17 is here:
> http://training.play-with-docker.com/ops-stage1/
> At about the 38 minute mark, on the topic of transitioning enterprise 
> apps to docker:
> "define your guardrails,  leave the db out in the VM."  Mike is a 
> docker evangelist.
>
>

Hmm - I don't think docker per se is the problem here - that 
default_statistics_target of 10000 is the more likely culprit. A minimal 
allowance of resources (e.g memory in this case) combined with hugely 
over spec'ed memory use (the default_statistics_target setting) is gonna 
trigger OOM for any environment.

regards

Mark