Re: Report a potential memory leak in setup_config() - Mailing list pgsql-bugs

From Daniel Gustafsson
Subject Re: Report a potential memory leak in setup_config()
Date
Msg-id A7070803-5A15-486E-AE04-ECC13CD10038@yesql.se
Whole thread Raw
In response to Report a potential memory leak in setup_config()  (wliang@stu.xidian.edu.cn)
Responses Re: Report a potential memory leak in setup_config()
List pgsql-bugs
> On 15 Feb 2022, at 02:49, wliang@stu.xidian.edu.cn wrote:

> Specifically, at line 1095, function pretty_wal_size() is called, which allocates a chunk of memory by using
pg_mallocand returns it. However, the return chunk is directly passed to snprintf as its 3rd parameter. As a result,
thereis a memory leak. 

PostgreSQL isn't all too concerned about small static leaks in short lived
programs, like initdb.  Memory will be freed shortly when the program exits.
Complicating the code to save 28 bytes seems hardly worth it, but if you feel
strongly about it I suggest proposing a patch to fix it.

--
Daniel Gustafsson        https://vmware.com/




pgsql-bugs by date:

Previous
From: hubert depesz lubaczewski
Date:
Subject: Re: BUG #17405: Minor upgrade from 12.9 to 12.10 works fine, but PSQL version shows "12.9"
Next
From: Troy Frericks
Date:
Subject: Re: A bug with the TimeStampTZ data type and the 'AT TIME ZONE' clause