Re: [PERFORM] OOM-killer issue with a specific query SOLVED

SOLVED On Tue, Dec 20, 2011 at 3:46 PM, Tom Lane - t...@sss.pgh.pa.us <+nabble+miller_2555+c5a65c2e1a.tgl#sss.pgh.pa...@spamgourmet.com> wrote: > nabble.30.miller_2...@spamgourmet.com writes: >> I've run EXPLAIN on the query, but AFAICS the query plan does not >> appear significantly different than

Re: [PERFORM] OOM-killer issue with a specific query 11 of 20)

On Tue, Dec 20, 2011 at 11:15 AM, F. BROUARD / SQLpro - sql...@club-internet.fr <+nabble+miller_2555+ca434688eb.sqlpro#club-internet...@spamgourmet.com> wrote: > I should think your query is not correct. > > Le 19/12/2011 16:52, nabble.30.miller_2...@spamgourmet.com a écrit : >> >> SELECT "bigint",

Re: [PERFORM] OOM-killer issue with a specific query 9 of 20)

On Tue, Dec 20, 2011 at 8:24 AM, Scott Marlowe - scott.marl...@gmail.com <+nabble+miller_2555+3b65e832a3.scott.marlowe#gmail@spamgourmet.com> wrote: > > On Mon, Dec 19, 2011 at 8:52 AM,   > wrote: > > I can probably fix by making the following sysctl adjustments: > > vm.overcommit_memory =

[PERFORM] OOM-killer issue with a specific query

Hi - I'm running into an OOM-killer issue when running a specific query (no virtual machine running) and, based on researching the issue, I can probably fix by making the following sysctl adjustments: vm.overcommit_memory = 2 vm.overcommit_ratio = 0 However, I am perplexed as to why I am ru