Re: BUG #6785: Memory Leak in plpgsql

From: Andres Freund <andres(at)2ndquadrant(dot)com>
To: Anderson Valadares <andervalbh(at)gmail(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #6785: Memory Leak in plpgsql
Date: 2012-07-30 15:56:22
Message-ID: 201207301756.22678.andres@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Hi,

On Monday, July 30, 2012 05:38:07 PM Anderson Valadares wrote:
> I understand, but the memory should not be returned after the execution of
> the function?
Well, that depends on how memory was allocated by the libc. When it used brk()
to allocate memory its rather likely that the memory cannot directly be
returned because some block of memory in the new memory is still used by some
permanent memory context.

> Below is the result of running with more than 55,000 calls.
>
> PID USER PR NI VIRT SWAP RES CODE DATA SHR S P %CPU %MEM TIME+
> COMMAND
> 618 postgres 15 0 1687m 1.2g 507m 4684 505m 3796 S 1 0.0 4.2 0:04.90
> postgres: postgres test [local] idle
Interesting. I just let the thing run - by accident - for 30+ minutes and it
still hovered at 96MB.

Greetings,

Andres
--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Bruce Momjian 2012-07-30 16:14:16 Re: BUG #6785: Memory Leak in plpgsql
Previous Message Anderson Valadares 2012-07-30 15:38:07 Re: BUG #6785: Memory Leak in plpgsql