Re: Addition to content - Mailing list pgsql-docs

From Bruce Momjian
Subject Re: Addition to content
Date
Msg-id 20201111193213.GA25840@momjian.us
Whole thread Raw
In response to Re: Addition to content  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-docs
On Mon, Nov  9, 2020 at 11:09:59AM -0500, Tom Lane wrote:
> PG Doc comments form <noreply@postgresql.org> writes:
> > I would be helpful to add that NULLIF and COALESCE need to be of same data
> > type. 
> 
> That's not actually a correct statement ... which I guess just reinforces
> your point that the behavior needs to be documented.

FYI, this was done in this commit:

    commit 24b83a5082
    Author: Tom Lane <tgl@sss.pgh.pa.us>
    Date:   Mon Nov 9 12:02:24 2020 -0500
    
        Doc: clarify data type behavior of COALESCE and NULLIF.
    
        After studying the code, NULLIF is a lot more subtle than you might
        have guessed.
    
        Discussion: https://postgr.es/m/160486028730.25500.15740897403028593550@wrigleys.postgresql.org

-- 
  Bruce Momjian  <bruce@momjian.us>        https://momjian.us
  EnterpriseDB                             https://enterprisedb.com

  The usefulness of a cup is in its emptiness, Bruce Lee




pgsql-docs by date:

Previous
From: Laurenz Albe
Date:
Subject: Re: Documentation of return values of range functions lower and upper
Next
From: Bruce Momjian
Date:
Subject: Re: What does "[backends] should seldom or never need to wait for a write to occur" mean?