Re: possible memory leak in Server Status window - Mailing list pgadmin-support

From Dave Page
Subject Re: possible memory leak in Server Status window
Date
Msg-id AANLkTikTGsF2gL434uCAiD_YO8ZDUeXA-SMnraJF2a86@mail.gmail.com
Whole thread Raw
In response to Re: possible memory leak in Server Status window  (Guillaume Lelarge <guillaume@lelarge.info>)
Responses Re: possible memory leak in Server Status window  (Peter Geoghegan <peter.geoghegan86@gmail.com>)
Re: possible memory leak in Server Status window  (Guillaume Lelarge <guillaume@lelarge.info>)
List pgadmin-support
On Sat, Feb 12, 2011 at 9:23 AM, Guillaume Lelarge
<guillaume@lelarge.info> wrote:
> I know Peter and Dave talked about some stuff I actually didn't
> understand, but it seems it would take some time to do. So, I prefer
> having this simple and effective fix right now :)

:-)

We were talking about smart pointers - basically, instead of doing
something like:

obj *foo = new obj();
...
<many lines of code and exit points>
...
delete foo;

You might do:

pg_smartptr<obj> foo;
...
<many lines of code and exit points>
...

Note the lack of a delete - that's the point here; it's not needed
because as soon as the smart pointer goes out of scope, it's
destructor will delete foo. That means you don't have to remember to
include the delete in each of the many exit points of the code.

See also http://en.wikipedia.org/wiki/Resource_Acquisition_Is_Initialization

-- 
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


pgadmin-support by date:

Previous
From: Vladimir Kokovic
Date:
Subject: Enpty field, grid editor, NOT NULL
Next
From: Dave Page
Date:
Subject: Re: Enpty field, grid editor, NOT NULL