Re: Running out of memory while making a join
| От | Carlos Henrique Reimer |
|---|---|
| Тема | Re: Running out of memory while making a join |
| Дата | |
| Msg-id | CAJnnue0MReCYWPB1_cdH+VK2fv-WXmjCSAvUFrcGKoK8x3M7FA@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Running out of memory while making a join (Craig Ringer <craig@2ndQuadrant.com>) |
| Ответы |
Re: Running out of memory while making a join
Re: Running out of memory while making a join |
| Список | pgsql-general |
Hi,
How is the best way to attach a debugger to the SELECT and identify why is it exhausting server storage.
Thank you in advance!
--
Reimer
47-3347-1724 47-9183-0547 msn: carlos.reimer@opendb.com.br
How is the best way to attach a debugger to the SELECT and identify why is it exhausting server storage.
Thank you in advance!
On Fri, Nov 9, 2012 at 4:10 AM, Craig Ringer <craig@2ndquadrant.com> wrote:
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
--
Reimer
47-3347-1724 47-9183-0547 msn: carlos.reimer@opendb.com.br
В списке pgsql-general по дате отправления: