From: Tom Lane <tgl@sss.pgh.pa.us>
To: pgsql-committers@lists.postgresql.org
Subject: pgsql: Fix minor memory leaks in pg_dump.
Date: Wed, 12 Feb 2025 21:07:50 +0000
Message-ID: <E1tiJxW-006nUB-9L@gemulon.postgresql.org> (raw)
Fix minor memory leaks in pg_dump.
Coverity reported the two oversights in getPublicationTables.
Valgrind found the one in determineNotNullFlags.
The mistakes in getPublicationTables seem too minor to be worth
back-patching. determineNotNullFlags could be run enough times
to matter, but that code is new in v18. So, no back-patch.
Branch
------
master
Details
-------
https://git.postgresql.org/pg/commitdiff/fcd77a6873018c06a34761b7be0c0d1fd847fdd5
Modified Files
--------------
src/bin/pg_dump/pg_dump.c | 3 +++
1 file changed, 3 insertions(+)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-committers@postgresql.org
Cc: tgl@sss.pgh.pa.us, pgsql-committers@lists.postgresql.org
Subject: Re: pgsql: Fix minor memory leaks in pg_dump.
In-Reply-To: <E1tiJxW-006nUB-9L@gemulon.postgresql.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox