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

From: Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-committers(at)postgresql(dot)org
Subject: Re: pgsql: Fix creative, but unportable, spelling of "ptr != NULL".
Date: 2016-12-13 04:06:15
Message-ID: cb54f4d5-5167-0a25-b22b-bd5b70df33be@lab.ntt.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Robert Haas 2016-12-13 13:20:11 pgsql: doc: Improve documentation related to table partitioning feature
Previous Message Petr Jelinek 2016-12-13 01:28:26 Re: pgsql: Add support for temporary replication slots