From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
---|---|
To: | m(dot)korotkov(at)postgrespro(dot)ru |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: pg_dump: fix memory leak |
Date: | 2025-08-29 07:13:01 |
Message-ID: | 9A56B32D-14F3-4EF0-A3B7-7065D7B5B53D@yesql.se |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> On 28 Aug 2025, at 16:14, m(dot)korotkov(at)postgrespro(dot)ru wrote:
>
> Hi all,
> I have found a potential memory leak in src/bin/pg_dump/dumputils.c in the function generate_restrict_key().
> Memory is allocated to the ret pointer if pg_strong_random returns false, and this leads to a memory leak.
> I have replaced the allocation to avoid this leak.
This is not actually a leak since the application will terminate immediately if
a restrict key cannot be generated. If you inspect the callsites you will see
this pattern:
if (!restrict_key)
restrict_key = generate_restrict_key();
if (!restrict_key)
pg_fatal("could not generate restrict key");
--
Daniel Gustafsson
From | Date | Subject | |
---|---|---|---|
Next Message | Andrey Borodin | 2025-08-29 07:20:40 | Re: IPC/MultixactCreation on the Standby server |
Previous Message | Bertrand Drouvot | 2025-08-29 07:05:14 | Re: Improve LWLock tranche name visibility across backends |