projects / postgresql.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: a924c32) | patch
Fix creative, but unportable, spelling of "ptr != NULL".
authorTom Lane <tgl@sss.pgh.pa.us>
Mon, 12 Dec 2016 16:23:23 +0000 (11:23 -0500)
committerTom Lane <tgl@sss.pgh.pa.us>
Mon, 12 Dec 2016 16:23:23 +0000 (11:23 -0500)
commit563d575fd73361f6118c13f2816988eba8e1f657
tree72f4d44c355c6c4f8c574c63be76abae4e0557fbtree
parenta924c327e2793d2025b19e18de7917110dc8afd8commit | diff
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.
src/backend/commands/tablecmds.c diff | blob | blame | history
This is the main PostgreSQL git repository.