Re: libpq: Remove redundant null pointer checks before free() - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: libpq: Remove redundant null pointer checks before free()
Date
Msg-id Yq1Drw2Ufo1GUVKy@paquier.xyz
Whole thread Raw
In response to Re: libpq: Remove redundant null pointer checks before free()  (Peter Eisentraut <peter.eisentraut@enterprisedb.com>)
Responses Re: libpq: Remove redundant null pointer checks before free()  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Fri, Jun 17, 2022 at 09:03:23PM +0200, Peter Eisentraut wrote:
> I'm pretty sure PostgreSQL code already depends on this behavior anyway.
> The code just isn't consistent about it.

In the frontend, I'd like to think that you are right and that we have
already some places doing that.  The backend is a different story,
like in GetMemoryChunkContext().  That should be easy enough to check
with some LD_PRELOAD wizardry, at least.
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: Add TAP test for auth_delay extension
Next
From: Tom Lane
Date:
Subject: Re: libpq: Remove redundant null pointer checks before free()