Re: Fix some resources leaks (src/bin/pg_basebackup/pg_createsubscriber.c)
| От | Tom Lane |
|---|---|
| Тема | Re: Fix some resources leaks (src/bin/pg_basebackup/pg_createsubscriber.c) |
| Дата | |
| Msg-id | 1139039.1711993923@sss.pgh.pa.us обсуждение исходный текст |
| Ответ на | Re: Fix some resources leaks (src/bin/pg_basebackup/pg_createsubscriber.c) ("Euler Taveira" <euler@eulerto.com>) |
| Ответы |
Re: Fix some resources leaks (src/bin/pg_basebackup/pg_createsubscriber.c)
|
| Список | pgsql-hackers |
"Euler Taveira" <euler@eulerto.com> writes:
> On Wed, Mar 27, 2024, at 8:50 PM, Ranier Vilela wrote:
>> Coverity has some reports in the new code
>> pg_createsubscriber.c
>> I think that Coverity is right.
> It depends on your "right" definition. If your program execution is ephemeral
> and the leak is just before exiting, do you think it's worth it?
I agree with Ranier, actually. The functions in question don't
exit() themselves, but return control to a caller that might or
might not choose to exit. I don't think they should be assuming
that an exit will happen promptly, even if that's true today.
The community Coverity run found a few additional leaks of the same
kind in that file. I pushed a merged fix for all of them.
regards, tom lane
В списке pgsql-hackers по дате отправления: