Re: postgresql 9.5 has ocuuered OOM - Mailing list pgsql-general

From Scott Marlowe
Subject Re: postgresql 9.5 has ocuuered OOM
Date
Msg-id CAOR=d=3aUco6DZyVMTW4cKPCtOi255B=Eg9F12kx_iN9tsOaWQ@mail.gmail.com
Whole thread Raw
In response to Re: postgresql 9.5 has ocuuered OOM  (Andreas Kretschmer <andreas@a-kretschmer.de>)
List pgsql-general
On Wed, Dec 20, 2017 at 9:25 AM, Andreas Kretschmer
<andreas@a-kretschmer.de> wrote:
>
>
> Am 20.12.2017 um 16:08 schrieb mark:
>>
>> postgresql process used over 70% of memory and occuered OOM.
>> what should I do to deal with this problem?
>
>
> https://www.postgresql.org/docs/current/static/kernel-resources.html
> 18.4.4. Linux Memory Overcommit

More specifically:
https://www.postgresql.org/docs/current/static/kernel-resources.html#LINUX-MEMORY-OVERCOMMIT

To reiterate the basic message there, at no time should the OS think
that killing big processes is OK. It is NOT. At no time should your OS
be terminating big processes all on its own.

Also it's far better to starve your work_mem and keep all the
processes running than to ever run any out of memory. But if one does
run out of memory it should only cause a problem for that one process,
not the backend writer etc.


pgsql-general by date:

Previous
From: "Rakesh Kumar"
Date:
Subject: Caching of sproc
Next
From: Andreas Kretschmer
Date:
Subject: Re: postgresql 9.5 has ocuuered OOM