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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Fix creative, but unportable, spelling of "ptr != NULL".
Date: 2016-12-12 16:23:38
Message-ID: E1cGTO6-0005Qx-0j@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

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(-)

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Robert Haas 2016-12-12 17:08:40 pgsql: psql: Fix incorrect version check for table partitining.
Previous Message Tom Lane 2016-12-12 15:55:44 Re: pgsql: Add support for temporary replication slots