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

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: Ranier Vilela <ranier(dot)vf(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Fix resource leak (src/backend/libpq/be-secure-common.c)
Date: 2024-04-02 18:31:48
Message-ID: DB8C32CC-83B9-4441-9E6A-626890B5E7F6@yesql.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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

--
Daniel Gustafsson

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David E. Wheeler 2024-04-02 18:38:56 RFC: Additional Directory for Extensions
Previous Message Tomas Vondra 2024-04-02 18:22:55 Re: using extended statistics to improve join estimates