| From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | Andreas Kretschmer <andreas(at)a-kretschmer(dot)de> |
| Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: postgresql 9.5 has ocuuered OOM |
| Date: | 2017-12-20 17:11:29 |
| Message-ID: | CAOR=d=3aUco6DZyVMTW4cKPCtOi255B=Eg9F12kx_iN9tsOaWQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wed, Dec 20, 2017 at 9:25 AM, Andreas Kretschmer
<andreas(at)a-kretschmer(dot)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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andreas Kretschmer | 2017-12-20 18:15:40 | Re: postgresql 9.5 has ocuuered OOM |
| Previous Message | Rakesh Kumar | 2017-12-20 17:09:56 | Caching of sproc |