Re: Avoid resource leak (contrib/postgres_fdw/connection.c)

From: Ranier Vilela <ranier(dot)vf(at)gmail(dot)com>
To: Matheus Alcantara <matheusssilv97(at)gmail(dot)com>
Cc: Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Avoid resource leak (contrib/postgres_fdw/connection.c)
Date: 2026-03-16 14:18:54
Message-ID: CAEudQAoBPKbb3XX1H8SV95BOyJYL5SjH2D7CHKgDFBXWeSg9Lg@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi.

Em seg., 16 de mar. de 2026 às 11:16, Matheus Alcantara <
matheusssilv97(at)gmail(dot)com> escreveu:

> On 16/03/26 08:45, Ranier Vilela wrote:
> > Hi.
> >
> > Per Coverity.
> >
> > CID 1645716: (#1 of 1): Resource leak (RESOURCE_LEAK)
> > 8. leaked_storage: Variable str going out of scope leaks the storage
> > str.data points to.
> >
> > The function *postgres_fdw_connection* leaks the contents of
> > var str.data
> > Once that function *cstring_to_text* palloc the contents
> > must be necessary to free the var str.data.
> >
> > patch attached.
> >
>
> Hi,
>
> Thanks for the patch, it looks correct to me. I've searched for this
> pattern `PG_RETURN_TEXT_P(cstring_to_text(.*.data` in other places and
> I've just found on postgres_fdw/connection.c
>
> I've also search for other cases of `return cstring_to_text(...)`
> usages and I didn't found anything that seems suspicious.
>
> Tests are also passing.
>
Thanks for taking a look.

best regards,
Ranier Vilela

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Matthias van de Meent 2026-03-16 14:21:18 Re: Adding REPACK [concurrently]
Previous Message Matheus Alcantara 2026-03-16 14:16:30 Re: Avoid resource leak (contrib/postgres_fdw/connection.c)