Re: Re all: Report some potential memory leak bugs in pg_dump.c
От | Julien Rouhaud |
---|---|
Тема | Re: Re all: Report some potential memory leak bugs in pg_dump.c |
Дата | |
Msg-id | 20220219111005.57bfn4qshuqxzkzi@jrouhaud обсуждение исходный текст |
Ответ на | Re all: Report some potential memory leak bugs in pg_dump.c (wliang@stu.xidian.edu.cn) |
Ответы |
Re: Re: Re all: Report some potential memory leak bugs in pg_dump.c
Re: Re all: Report some potential memory leak bugs in pg_dump.c |
Список | pgsql-bugs |
Hi, On Sat, Feb 19, 2022 at 04:04:38PM +0800, wliang@stu.xidian.edu.cn wrote: > However, there are also some potential leaks caused by convertTSFunction() > rather than getFormattedTypeName(). Besides, in convertTSFunction(), there > are no any comment to say that the memory should not be freed by the caller. Indeed this function doesn't cache anything and explicitly calls pg_strdup. Here the amount of leaked memory is likely to be very small (I never heard of people having thousands of text search templates or parsers), and pg_dump isn't a long lived process so probably no one thought it was worth to extra code to free that memory, which I agree with.
В списке pgsql-bugs по дате отправления: