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

From: Frank van Vugt <ftm(dot)van(dot)vugt(at)foxi(dot)nl>
To: Valentine Gogichashvili <valgog(at)gmail(dot)com>
Cc: PostgreSQL Bugs <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: array_agg() on a set larger than some arbitrary(?) limit causes runaway memory usage and eventually memory exhaustion
Date: 2013-10-20 08:26:39
Message-ID: 2334937.gaPyc11YQv@techfox.foxi
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Hi Valentine,

Op zaterdag 19 oktober 2013 21:02:25 schreef Valentine Gogichashvili:
> this is a little bit not relevant to the question itself. But to prevent OOM
> killer from currupting your database please consider this for your
> production environments:

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.

--

Best,

Frank.

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Frank van Vugt 2013-10-20 08:26:53 Re: array_agg() on a set larger than some arbitrary(?) limit causes runaway memory usage and eventually memory exhaustion
Previous Message Tomas Vondra 2013-10-20 02:48:01 Re: array_agg() on a set larger than some arbitrary(?) limit causes runaway memory usage and eventually memory exhaustion