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

From Peter Eisentraut
Subject Change pfree to accept NULL argument
Date
Msg-id cf26e970-8e92-59f1-247a-aa265235075b@enterprisedb.com
Whole thread Raw
Responses Re: Change pfree to accept NULL argument
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.)


[0]: https://www.postgresql.org/message-id/1074830.1655442689@sss.pgh.pa.us
Attachment

pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: pg_stat_have_stats() returns true for dropped indexes (or for index creation transaction rolled back)
Next
From: Tom Lane
Date:
Subject: Re: Change pfree to accept NULL argument