Re: Avoid resource leak (src/test/regress/pg_regress.c) - Mailing list pgsql-hackers

From Ranier Vilela
Subject Re: Avoid resource leak (src/test/regress/pg_regress.c)
Date
Msg-id CAEudQArofjr3a235eN_nwmAztxB3pc01o4gHQnn3VREOYsf1XQ@mail.gmail.com
Whole thread Raw
In response to Re: Avoid resource leak (src/test/regress/pg_regress.c)  (Álvaro Herrera <alvherre@kurilemu.de>)
List pgsql-hackers
Em sex., 24 de out. de 2025 às 09:21, Álvaro Herrera <alvherre@kurilemu.de> escreveu:
On 2025-Oct-24, Ranier Vilela wrote:

> Em sex., 24 de out. de 2025 às 03:03, Michael Paquier
> <michael@paquier.xyz> escreveu:

> > This is just one of them, allocated in the context of what is a
> > short-term execution.
>
> In this case, I believe pg_regress is run, thousands of times, on
> hundreds of computers.

Yes, but the memory is released at the end of the program execution,
every single one of those times.
Yeah, for sure.
But not before thousands of tests were carried out.

The allocated memory is useless until the program exits.
According to getaddrinfo documentation:
"The getaddrinfo() function allocates and initializes a linked list
       of addrinfo structures, one for each network address that matches       node and service, subject to any restrictions imposed by hints,       and returns a pointer to the start of the list in res.  The items       in the linked list are linked by the ai_next field.
       There are several reasons why the linked list may have more than       one addrinfo structure, including: the network host is multihomed,       accessible over multiple protocols" 

best regards
Ranier Vilela

pgsql-hackers by date:

Previous
From: Tomas Vondra
Date:
Subject: Re: WIP: parallel GiST index builds
Next
From: Andres Freund
Date:
Subject: Re: use SIMD in GetPrivateRefCountEntry()