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

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Daniel Gustafsson <daniel(at)yesql(dot)se>
Cc: Ranier Vilela <ranier(dot)vf(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Fix resource leak (src/backend/libpq/be-secure-common.c)
Date: 2024-05-14 06:03:22
Message-ID: ZkL-ql8i7B-UCnUj@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, May 13, 2024 at 08:06:57PM +0200, Daniel Gustafsson wrote:
>> Any chance we'll have these fixes in v17?
>
> Nice timing, I was actually rebasing them today to get them committed.

Looks sensible seen from here, as these paths could use a LOG or rely
on a memory context permanent to the backend causing junk to be
accumulated. It's not that much, still that would accumulate.
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David Rowley 2024-05-14 06:16:26 Re: explain format json, unit for serialize and memory are different.
Previous Message jian he 2024-05-14 05:40:59 Bibliography section, some references cannot be found