[COMMITTERS] pgsql: Fix creative, but unportable, spelling of "ptr != NULL". - Mailing list pgsql-committers

From Tom Lane
Subject [COMMITTERS] pgsql: Fix creative, but unportable, spelling of "ptr != NULL".
Date
Msg-id E1cGTO6-0005Qx-0j@gemulon.postgresql.org
Whole thread Raw
Responses Re: [COMMITTERS] pgsql: Fix creative, but unportable, spelling of"ptr != NULL".
List 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(-)


pgsql-committers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [COMMITTERS] pgsql: Add support for temporary replication slots
Next
From: Robert Haas
Date:
Subject: [COMMITTERS] pgsql: psql: Fix incorrect version check for table partitining.