pgsql: Avoid memory leak in rmtree() when path cannot be opened - Mailing list pgsql-committers

From Michael Paquier
Subject pgsql: Avoid memory leak in rmtree() when path cannot be opened
Date
Msg-id E1qQImS-0025WV-8b@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
Avoid memory leak in rmtree() when path cannot be opened

An allocation done for the directory names to recurse into for their
deletion was done before OPENDIR(), so, assuming that a failure happens,
this could leak a bit of memory.

Author: Ranier Vilela
Reviewed-by: Daniel Gustafsson
Discussion: https://postgr.es/m/CAEudQAoN3-2ZKBALThnEk_q2hu8En5A0WG9O+5siJTQKVZzoWQ@mail.gmail.com

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/f1e9f6bbfa536992eac6c094882b3afcd9e90fb4

Modified Files
--------------
src/common/rmtree.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)


pgsql-committers by date:

Previous
From: Michael Paquier
Date:
Subject: pgsql: Fix pg_rewind with in-place tablespaces when source is remote
Next
From: Michael Paquier
Date:
Subject: pgsql: Add WAIT_EVENT_{CLASS,ID}_MASK in wait_event.c