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

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: Michael Paquier <michael(at)paquier(dot)xyz>
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 10:21:31
Message-ID: 160D403D-9DD8-42E8-AD26-7261DC243156@yesql.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On 14 May 2024, at 08:03, Michael Paquier <michael(at)paquier(dot)xyz> wrote:
>
> 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.

Pushed.

--
Daniel Gustafsson

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Ilyasov Ian 2024-05-14 10:22:29 Fix src/test/subscription/t/029_on_error.pl test when wal_debug is enabled
Previous Message Jakub Wartak 2024-05-14 10:12:06 Re: elog/ereport VS misleading backtrace_function function address