From: | "Matt Magoffin" <postgresql(dot)org(at)msqr(dot)us> |
---|---|
To: | "Stephen Frost" <sfrost(at)snowman(dot)net> |
Cc: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Out of memory on SELECT in 8.3.5 |
Date: | 2009-02-09 20:25:36 |
Message-ID: | 49338.192.168.1.106.1234211136.squirrel@msqr.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
> * Matt Magoffin (postgresql(dot)org(at)msqr(dot)us) wrote:
>> [root(at)170226-db7 ~]# cat /proc/meminfo
>> CommitLimit: 10312588 kB
>> Committed_AS: 9760756 kB
>
> I suspect this may be it... Apparently, while you're only using about
> 2G, you've got 10G or so of outstanding commitments, and Linux is
> refusing to allocate more.
>
> You probably want to up your overcommit_ratio, esp. in light of the fact
> that you've only got 2G of swap on this box. I'd probably say up it to
> 80, which would give you 14.8G of commitable memory, leaving some room
> in-memory (1.2G) for cache/buffers and whatnot. Alternativly, you could
> go for 90, which would allow commits up to 16.4G, so if everyone used
> all their memory, you'd be into swap.
Thanks for the advice. Should we have more than 2GB of swap available? I
thought the goal for a Postgres system was to avoid swap use at all cost?
Would it be better for us to add more swap, or adjust this
overcommit_ratio as you discuss?
Regards,
Matt
From | Date | Subject | |
---|---|---|---|
Next Message | Matt Magoffin | 2009-02-09 20:32:41 | Re: Out of memory on SELECT in 8.3.5 |
Previous Message | Matt Magoffin | 2009-02-09 20:21:25 | Re: Out of memory on SELECT in 8.3.5 |