Plug some trivial memory leaks in pg_dump and pg_upgrade. There's no point in trying to free every small allocation in these programs that are used in a one-shot fashion, but these ones seems like an improvement on readability grounds.
Michael Paquier, per Coverity report. Branch ------ master Details ------- http://git.postgresql.org/pg/commitdiff/f712289ffad7c3fb6eb3be4f81adb0aa0981c9f7 Modified Files -------------- src/bin/pg_dump/pg_dump.c | 28 ++++++++++++++++------------ src/bin/pg_dump/pg_dumpall.c | 7 +++++++ src/bin/pg_upgrade/check.c | 6 ++++++ 3 files changed, 29 insertions(+), 12 deletions(-) -- Sent via pgsql-committers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
