Re: Running out of memory while making a join

From: Craig Ringer <craig(at)2ndQuadrant(dot)com>
To: Carlos Henrique Reimer <carlos(dot)reimer(at)opendb(dot)com(dot)br>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Running out of memory while making a join
Date: 2012-11-09 06:10:29
Message-ID: 509C9E55.6090004@2ndQuadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 11/08/2012 11:35 PM, Carlos Henrique Reimer wrote:
> Hi Craig,
>
> work_mem is defined with 10MB and yes, there are triggers defined on
> both tables

Come to think of it, the triggers don't make any difference to memory
use for a SELECT anyway.

Your work_mem is perfectly reasonable.

The plan looks pretty harsh, with that big nested loop, but I'm not
aware of anything that'd cause that to run out of memory.

Personally I'd be attaching a debugger to it and seeing what it was
doing while it ran. I'm sure there are smarter ways to trace where the
memory use is going, though.

--
Craig Ringer

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2012-11-09 06:12:19 Re: Using hstore, json, lo, etc from C extensions?
Previous Message Craig Ringer 2012-11-09 06:05:54 Using hstore, json, lo, etc from C extensions?