Postgres Pro
Downloads
Home   >   mailing lists

Re: Avoid possible memory leak (src/common/rmtree.c) - Mailing list pgsql-hackers

From Daniel Gustafsson
Subject Re: Avoid possible memory leak (src/common/rmtree.c)
Date
Msg-id 3FE85611-3B27-4E88-B61B-36FEDE3F2C59@yesql.se
Whole thread Raw
In response to Avoid possible memory leak (src/common/rmtree.c)  (Ranier Vilela <ranier.vf@gmail.com>)
Responses Re: Avoid possible memory leak (src/common/rmtree.c)  (Michael Paquier <michael@paquier.xyz>)
List pgsql-hackers
Tree view 
> On 25 Jul 2023, at 16:31, Ranier Vilela <ranier.vf@gmail.com> wrote:

> rmtree function can leak 64 bytes per call,
> when it can't open a directory.

Skimming the tree there doesn't seem to be any callers which aren't exiting or
ereporting on failure so the real-world impact seems low.  That being said,
silencing static analyzers could be reason enough to delay allocation.

--
Daniel Gustafsson

pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: [PATCH] Small refactoring of inval.c and inval.h
Next
From: Melih Mutlu
Date:
Subject: Re: [PATCH] Reuse Workers and Replication Slots during Logical Replication