| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | greigwise <greigwise(at)comcast(dot)net>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Out of Memory |
| Date: | 2018-09-26 18:05:56 |
| Message-ID: | 824208787ca76bb05c1076b72629e394c6ed660b.camel@cybertec.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
greigwise wrote:
> All right.. one more thing here. Any suggestions for how to set overcommit
> on a postgres db server with 16 GB of RAM and no swap? I think I want
> vm.overcommit_memory = 2, as I understand that prevents the OOM killer from
> zapping me. Is 100% the right way to go for overcommit_ratio? Is there a
> drawback to this?
vm.overcommit_memory = 2
vm_overcommit_ratio = 100
Linux commits (swap * overcommit_ratio * RAM / 100),
so without any swap the correct value would be 100.
I don't know how safe it is to got entirely without swap.
I would add a little bit just to be sure.
Yours,
Laurenz Albe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | jimmy | 2018-09-27 01:10:40 | Re:Re: how to clean the cache from databases and operating system |
| Previous Message | Pierre Timmermans | 2018-09-26 17:19:44 | Re: Setting up continuous archiving |