re: Change pfree to accept NULL argument - Mailing list pgsql-hackers

From Ranier Vilela
Subject re: Change pfree to accept NULL argument
Date
Msg-id CAEudQArevG-VO+x2eyk12UUnY192nBdBnwFrcXNyER1FasxChw@mail.gmail.com
Whole thread Raw
In response to Change pfree to accept NULL argument  (Peter Eisentraut <peter.eisentraut@enterprisedb.com>)
List pgsql-hackers

>Per discussion in [0], here is a patch set that allows pfree() to accept
>a NULL argument, like free() does.

>Also, a patch that removes the now-unnecessary null pointer checks
>before calling pfree(). And a few patches that do the same for some
>other functions that I found around. (The one with FreeDir() is perhaps
>a bit arguable, since FreeDir() wraps closedir() which does *not* accept
>NULL arguments. Also, neither FreeFile() nor the underlying fclose()
>accept NULL.)

Hi Peter,

+1

However, after a quick review, I noticed some cases of PQ freemen missing.
I took the liberty of making a v1, attached.

regards,

Ranier Vilela

Attachment

pgsql-hackers by date:

Previous
From: Pavel Stehule
Date:
Subject: Re: Schema variables - new implementation for Postgres 15
Next
From: Nikita Malakhov
Date:
Subject: Re: [PATCH] ALTER TABLE ... SET STORAGE default