Re: Fix PGresult leak in pg_dump during binary upgrade - Mailing list pgsql-hackers

From Daniel Gustafsson
Subject Re: Fix PGresult leak in pg_dump during binary upgrade
Date
Msg-id 0B2CE973-F8FA-4F9D-9F49-2D95468AC259@yesql.se
Whole thread Raw
In response to Re: Fix PGresult leak in pg_dump during binary upgrade  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
> On 15 May 2024, at 20:46, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
> Daniel Gustafsson <daniel@yesql.se> writes:
>> While looking at pg_dump performance today I noticed that pg_dump fails to
>> clear query results in binary_upgrade_set_pg_class_oids during binary upgrade
>> mode.  9a974cbcba00 moved the query to the outer block, but left the PQclear
>> and query buffer destruction in the is_index conditional, making it not always
>> be executed.  353708e1fb2d fixed the leak of the query buffer but left the
>> PGresult leak.  The attached fixes the PGresult leak which when upgrading large
>> schemas can be non-trivial.
>
> +1 --- in 353708e1f I was just fixing what Coverity complained about.
> I wonder why it missed this; it does seem to understand that PGresult
> leaks are a thing.  But anyway, I missed it too.

Done, backpatched to v15. Thanks for review!

--
Daniel Gustafsson




pgsql-hackers by date:

Previous
From: Nathan Bossart
Date:
Subject: Re: Why does pgindent's README say to download typedefs.list from the buildfarm?
Next
From: Nathan Bossart
Date:
Subject: Re: recovery modules