Re: pg_dump: fix memory leak - Mailing list pgsql-hackers

From m.korotkov@postgrespro.ru
Subject Re: pg_dump: fix memory leak
Date
Msg-id 0a1c923797fc258576719afc6f61e9f0@postgrespro.ru
Whole thread Raw
In response to Re: pg_dump: fix memory leak  (Daniel Gustafsson <daniel@yesql.se>)
List 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.korotkov@postgrespro.ru



pgsql-hackers by date:

Previous
From: Pavel Stehule
Date:
Subject: Re: pgbench: extend variable usage in scripts
Next
From: Peter Eisentraut
Date:
Subject: Re: headerscheck warnings with late-model gcc