Re: Memory leak fixes for pg_dump, pg_dumpall, initdb and pg_upgrade - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: Memory leak fixes for pg_dump, pg_dumpall, initdb and pg_upgrade
Date
Msg-id CAB7nPqQPJFM16M8jzSVGudT_0FT3Z_4QgCjs29O=i+OZRiHb4Q@mail.gmail.com
Whole thread Raw
In response to Memory leak fixes for pg_dump, pg_dumpall, initdb and pg_upgrade  (Michael Paquier <michael.paquier@gmail.com>)
Responses Re: Memory leak fixes for pg_dump, pg_dumpall, initdb and pg_upgrade  (Michael Paquier <michael.paquier@gmail.com>)
List pgsql-hackers
On Mon, Jun 8, 2015 at 3:48 PM, Michael Paquier
<michael.paquier@gmail.com> wrote:
> Hi all,
>
> Please find attached a set of fixes for a couple of things in src/bin:
> - pg_dump/pg_dumpall:
> -- getFormattedTypeName, convertTSFunction and myFormatType return
> strdup'd results that are never free'd.
> -- convertTSFunction returns const char. I fail to see the point of
> that... In my opinion we are fine with just returning a char pointer,
> which is strdup'd so as it can be freed by the caller.
> - initdb's and pg_regress' use getaddrinfo, but do not free the
> returned result with freeaddrinfo().
> - Coverity noticed on the way some leaked memory in pg_upgrade's
> equivalent_locale().
>
> Those issues have been mostly spotted by Coverity, I may have spotted
> some of them while looking at similar code paths... In any case that's
> Coverity's win ;)

Attached are new patches, I simplified the use of free in the fixes of
pg_dumpall.
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: Geoff Winkless
Date:
Subject: Re: [CORE] Restore-reliability mode
Next
From: Michael Paquier
Date:
Subject: Re: Memory leak fixes for pg_dump, pg_dumpall, initdb and pg_upgrade