| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Tomas Vondra <tv(at)fuzzy(dot)cz>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: excessive amounts of consumed memory (RSS), triggering OOM killer |
| Date: | 2014-12-01 23:31:19 |
| Message-ID: | 547CFA47.2060607@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 12/01/2014 05:39 PM, Tomas Vondra wrote:
> Hi all,
>
> while working on the patch decreasing amount of memory consumed by
> array_agg [1], I've ran into some strange OOM issues. Reproducing them
> using the attached SQL script is rather simple.
>
> [1] https://commitfest.postgresql.org/action/patch_view?id=1652
>
> At first I thought there's some rare hidden memory leak, but I'm pretty
> sure that's not the case. I've even put some explicit counters into
> aset.c counting allocated/freed blocks, and it seems to be working just
> fine (and matching the context tree perfectly). So no memory leak.
Doesn't this line:
TopMemoryContext: 136614192 total in 16678 blocks; 136005936 free (500017 chunks); 608256 used
look pretty suspicious?
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tomas Vondra | 2014-12-02 00:26:00 | Re: excessive amounts of consumed memory (RSS), triggering OOM killer |
| Previous Message | Tomas Vondra | 2014-12-01 22:39:46 | excessive amounts of consumed memory (RSS), triggering OOM killer |