Thread: [COMMITTERS] pgsql: Fix creative, but unportable, spelling of "ptr != NULL".

Fix creative, but unportable, spelling of "ptr != NULL".

Or at least I suppose that's what was really meant here.  But even
aside from the not-per-project-style use of "0" to mean "NULL",
I doubt it's safe to assume that all valid pointers are > NULL.
Per buildfarm member pademelon.

Branch
------
master

Details
-------
http://git.postgresql.org/pg/commitdiff/563d575fd73361f6118c13f2816988eba8e1f657

Modified Files
--------------
src/backend/commands/tablecmds.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)

On 2016/12/13 1:23, Tom Lane wrote:
> Fix creative, but unportable, spelling of "ptr != NULL".
>
> Or at least I suppose that's what was really meant here.  But even
> aside from the not-per-project-style use of "0" to mean "NULL",
> I doubt it's safe to assume that all valid pointers are > NULL.
> Per buildfarm member pademelon.

Oops, that was definitely unintentional.  Thanks for fixing!

Thanks,
Amit