Re: pg_dump: fix memory leak

From: m(dot)korotkov(at)postgrespro(dot)ru
To: Daniel Gustafsson <daniel(at)yesql(dot)se>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_dump: fix memory leak
Date: 2025-08-29 07:36:22
Message-ID: 0a1c923797fc258576719afc6f61e9f0@postgrespro.ru
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Daniel Gustafsson wrote 2025-08-29 10:13:
> This is not actually a leak since the application will terminate
> immediately if
> a restrict key cannot be generated.
I agree that the current usage of the function does not present a
problem, but there is no certainty that this situation will remain
unchanged. In my view, it would be prudent to explicitly release the
memory.
---
Best regards, Korotkov Maksim
PostgresPro
m(dot)korotkov(at)postgrespro(dot)ru

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2025-08-29 07:37:36 Re: headerscheck warnings with late-model gcc
Previous Message Роман Хапов 2025-08-29 07:31:21 Re: pg_dump: fix memory leak