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

From Amit Langote
Subject Re: [COMMITTERS] pgsql: Fix creative, but unportable, spelling of"ptr != NULL".
Date
Msg-id cb54f4d5-5167-0a25-b22b-bd5b70df33be@lab.ntt.co.jp
Whole thread Raw
In response to [COMMITTERS] pgsql: Fix creative, but unportable, spelling of "ptr != NULL".  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-committers
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




pgsql-committers by date:

Previous
From: Petr Jelinek
Date:
Subject: Re: [COMMITTERS] pgsql: Add support for temporary replication slots
Next
From: Robert Haas
Date:
Subject: [COMMITTERS] pgsql: doc: Improve documentation related to table partitioningfeature