Re: Fix resource leak (src/backend/libpq/be-secure-common.c)

From: Ranier Vilela <ranier(dot)vf(at)gmail(dot)com>
To: Daniel Gustafsson <daniel(at)yesql(dot)se>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Fix resource leak (src/backend/libpq/be-secure-common.c)
Date: 2024-05-13 18:05:32
Message-ID: CAEudQAoQ6pVAu4JS-KPgkPW_Nvb0bUbjGtYEwa7ADGOxQ=KVug@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Em qua., 10 de abr. de 2024 às 15:33, Daniel Gustafsson <daniel(at)yesql(dot)se>
escreveu:

> On 10 Apr 2024, at 20:31, Ranier Vilela <ranier(dot)vf(at)gmail(dot)com> wrote:
>
> Em ter., 2 de abr. de 2024 às 15:31, Daniel Gustafsson <daniel(at)yesql(dot)se>
> escreveu:
>
>> > On 2 Apr 2024, at 20:13, Ranier Vilela <ranier(dot)vf(at)gmail(dot)com> wrote:
>>
>> > Fix by freeing the pointer, like pclose_check (src/common/exec.c)
>> similar case.
>>
>> Off the cuff, seems reasonable when loglevel is LOG.
>>
>
> Per Coverity.
>
> Another case of resource leak, when loglevel is LOG.
> In the function shell_archive_file (src/backend/archive/shell_archive.c)
> The pointer *xlogarchcmd* is not freed.
>
>
> Thanks, I'll have a look. I've left this for post-freeze on purpose to not
> cause unnecessary rebasing. Will take a look over the next few days unless
> beaten to it.
>
Any chance we'll have these fixes in v17?

best regards,
Ranier Vilela

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Daniel Gustafsson 2024-05-13 18:06:57 Re: Fix resource leak (src/backend/libpq/be-secure-common.c)
Previous Message Ranier Vilela 2024-05-13 18:02:05 Re: Fix out-of-bounds in the function GetCommandTagName