Re: Abnormally high memory usage/OOM triggered

From: scott ribe <scott_ribe(at)elevated-dev(dot)com>
To: Davlet Panech <dpanech(at)gmail(dot)com>
Cc: pgsql-admin(at)lists(dot)postgresql(dot)org
Subject: Re: Abnormally high memory usage/OOM triggered
Date: 2018-01-17 22:57:33
Message-ID: 5E0AB8DB-F13B-41BF-843A-FE64FBE9C097@elevated-dev.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

On Jan 17, 2018, at 2:57 PM, Davlet Panech <dpanech(at)gmail(dot)com> wrote:
>
> Does my configuration look reasonable? I just don't understand how it could possibly use up 19 GB of memory based on the configuration below. Is there a memory leak in there somewhere?

It does seem awfully high, but... An update can involve a join across multiple tables. Or an update can run a trigger which can cascade. Either of those could result in an "accidental cross product" join, which can always blow up memory.

--
Scott Ribe
https://www.linkedin.com/in/scottribe/
(303) 722-0567

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Tom Lane 2018-01-18 00:15:20 Re: Abnormally high memory usage/OOM triggered
Previous Message Davlet Panech 2018-01-17 21:57:28 Abnormally high memory usage/OOM triggered