From: | Davlet Panech <dpanech(at)gmail(dot)com> |
---|---|
To: | pgsql-admin(at)lists(dot)postgresql(dot)org |
Subject: | Re: Abnormally high memory usage/OOM triggered |
Date: | 2018-01-18 17:13:33 |
Message-ID: | 15a90b55-5151-ce22-16ee-7ff883e5eb97@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On 1/17/2018 5:57 PM, scott ribe wrote:
> 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.
There must be a way to put an upper limit on memory even for such cases.
I was under the impression that parameters such as "work_mem" serve that
purpose, is that not the case? So an "accidental cross product" join's
memory usage is unbounded? It can't be... could somebody confirm this
please?
Thanks,
D.
From | Date | Subject | |
---|---|---|---|
Next Message | scott ribe | 2018-01-18 17:34:59 | Re: Abnormally high memory usage/OOM triggered |
Previous Message | Laurenz Albe | 2018-01-18 13:08:11 | Re: Issue with grant & revoke |