Re: Out of Memory errors are frustrating as heck! - Mailing list pgsql-performance

From Jeff Janes
Subject Re: Out of Memory errors are frustrating as heck!
Date
Msg-id CAMkU=1zV2ftAtSNjVaJLoXpUj0NLj4bPqmPm6gwN1Ygktni59g@mail.gmail.com
Whole thread Raw
In response to Out of Memory errors are frustrating as heck!  (Gunther <raj@gusw.net>)
Responses Re: Out of Memory errors are frustrating as heck!
List pgsql-performance
On Sun, Apr 14, 2019 at 4:51 PM Gunther <raj@gusw.net> wrote:

For weeks now, I am banging my head at an "out of memory" situation. There is only one query I am running on an 8 GB system, whatever I try, I get knocked out on this out of memory.

Is PostgreSQL throwing an error with OOM, or is getting killed -9 by the OOM killer?  Do you get a core file you can inspect with gdb?

You might want to see the query, but it is a huge plan, and I can't really break this down. It shouldn't matter though. But just so you can get a glimpse here is the plan:

Insert on businessoperation  (cost=5358849.28..5361878.44 rows=34619 width=1197) ->  Unique  (cost=5358849.28..5361532.25 rows=34619 width=1197)       

Maybe it is memory for trigger or constraint checking, although I don't know why that would appear instantly.  What triggers or constraints do you have on businessoperation? 

What if you just run the SELECT without the INSERT?  Or insert into a temp table rather than into businessoperation?  And if that doesn't crash, what if you then insert to businessoperation from the temp table?
 
Also, what version?

Cheers,

Jeff

pgsql-performance by date:

Previous
From: Tom Lane
Date:
Subject: Re: Out of Memory errors are frustrating as heck!
Next
From: Gunther
Date:
Subject: Re: Out of Memory errors are frustrating as heck!