Re: array_agg() on a set larger than some arbitrary(?) limit causes runaway memory usage and eventually memory exhaustion - Mailing list pgsql-bugs

From Valentine Gogichashvili
Subject Re: array_agg() on a set larger than some arbitrary(?) limit causes runaway memory usage and eventually memory exhaustion
Date
Msg-id CAP93muVkB17HZYUufcvK8BBHkyPhvVmMyaXUDxPh+1JLwQVS+A@mail.gmail.com
Whole thread Raw
In response to Re: array_agg() on a set larger than some arbitrary(?) limit causes runaway memory usage and eventually memory exhaustion  (Frank van Vugt <ftm.van.vugt@foxi.nl>)
Responses Re: array_agg() on a set larger than some arbitrary(?) limit causes runaway memory usage and eventually memory exhaustion
List pgsql-bugs
Hi Frank,

On Sun, Oct 20, 2013 at 10:26 AM, Frank van Vugt <ftm.van.vugt@foxi.nl>wrote:

> Sure, I understand why you'd want to mention this 'on the side', but I'm
> aware
> of OOM-tuning. In production, I use it wherever it's _really_ needed, but
> mind
> that the oom-killer in newer kernels is already selecting processes a bit
> smarter than it used to. In the example I gave, the correct child process
> was
> killed.
>
> I personally prefer to see ERROR: out of memory, coming from Postgres,
then OOM killing processes, that it thinks are to be killed :)

Apropos, how does the string_agg aggregate behave in your example? Will be
nice to know without experimenting myself and looking into the sources :)

Regards,

-- Valentine

pgsql-bugs by date:

Previous
From: "Tomas Vondra"
Date:
Subject: Re: array_agg() on a set larger than some arbitrary(?) limit causes runaway memory usage and eventually memory exhaustion
Next
From: jackie.qq.chang@gmail.com
Date:
Subject: BUG #8540: Avoid sscanf buffer overflow