Re: Report a potential memory leak in setup_config()
| От | Daniel Gustafsson |
|---|---|
| Тема | Re: Report a potential memory leak in setup_config() |
| Дата | |
| Msg-id | A7070803-5A15-486E-AE04-ECC13CD10038@yesql.se обсуждение исходный текст |
| Ответ на | Report a potential memory leak in setup_config() (wliang@stu.xidian.edu.cn) |
| Ответы |
Re: Report a potential memory leak in setup_config()
|
| Список | 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 по дате отправления: