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: Michael Paquier <michael(at)paquier(dot)xyz>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Fix resource leak (src/backend/libpq/be-secure-common.c)
Date: 2024-05-14 11:03:57
Message-ID: CAEudQAodTbq9B4gg9BoLdVP9Yu_s5iyCSZnTdMyyJN1BRqY-KA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Em ter., 14 de mai. de 2024 às 07:21, Daniel Gustafsson <daniel(at)yesql(dot)se>
escreveu:

> > 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.
>
Thanks Daniel.

best regards,
Ranier Vilela

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Aleksander Alekseev 2024-05-14 11:18:33 Re: Postgres and --config-file option
Previous Message David Rowley 2024-05-14 10:58:29 Re: Incorrect Assert in BufFileSize()?