BUG #8013: Memory leak - Mailing list pgsql-bugs

From Jeff Janes
Subject BUG #8013: Memory leak
Date
Msg-id CAMkU=1yjrO-kgnhh+1CCWRE0wpMp678tup_5oR-hVAZy=pjE8w@mail.gmail.com
Whole thread Raw
In response to Re: BUG #8013: Memory leak  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
On Sunday, March 31, 2013, Tom Lane wrote:

>
> A different line of thought is that you might have set work_mem to
> an unreasonably large value --- the sort step will happily try to
> consume work_mem worth of memory.
>

I don't think that that can be the problem here, because memtuples can
never be more than 1GB even if work_mem is much larger than that.  Even if
his sort is using pass-by-reference (I don't think it would be), they
should be skinny enough that that limitation should prevent it from blowing
out memory.

Cheers,

Jeff

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #8013: Memory leak
Next
From: Daniel Farina
Date:
Subject: Re: BUG #8013: Memory leak