From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Fix PGresult leak in pg_dump during binary upgrade |
Date: | 2024-05-15 21:04:59 |
Message-ID: | 0B2CE973-F8FA-4F9D-9F49-2D95468AC259@yesql.se |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> On 15 May 2024, at 20:46, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> Daniel Gustafsson <daniel(at)yesql(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Nathan Bossart | 2024-05-15 21:10:39 | Re: recovery modules |
Previous Message | Nathan Bossart | 2024-05-15 20:54:27 | Re: Why does pgindent's README say to download typedefs.list from the buildfarm? |