Re: safer node casting

From: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andres Freund <andres(at)anarazel(dot)de>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: safer node casting
Date: 2017-02-24 16:17:26
Message-ID: c9086459-11f4-e2ee-2a41-4d94b62fd3e4@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2/24/17 10:54, Tom Lane wrote:
> Andres Freund <andres(at)anarazel(dot)de> writes:
>> Those aren't actually equivalent, because of the !nodeptr. IsA() crashes
>> for NULL pointers, but the new code won't. Which means 9ba8a9ce4548b et
>> al actually weakened some asserts.
>
>> Should we perhaps have one NULL accepting version (castNodeNull?) and
>> one that separately asserts that ptr != NULL?
>
> -1 ... if you're going to use something in a way that requires it not to
> be null, your code will crash quite efficiently on a null, with or
> without an assert. I don't think we need the extra cogitive burden of
> two distinct macros for this.

I think we should just add some Assert(thepointer) where necessary.

--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2017-02-24 16:18:18 Re: Make subquery alias optional in FROM clause
Previous Message Robert Haas 2017-02-24 16:17:05 Re: Patch: Write Amplification Reduction Method (WARM)