Re: Issue with point_ops and NaN - Mailing list pgsql-hackers

From Laurenz Albe
Subject Re: Issue with point_ops and NaN
Date
Msg-id f4203680196509a76f89fb7f60e5e944cd6fe935.camel@cybertec.at
Whole thread Raw
In response to Re: Issue with point_ops and NaN  (Kyotaro Horiguchi <horikyota.ntt@gmail.com>)
List pgsql-hackers
On Thu, 2021-04-01 at 09:35 +0900, Kyotaro Horiguchi wrote:
> > > > > > > > SELECT point('NaN','NaN') <@ polygon('(0,0),(1,0),(1,1),(0,0)');
> > > > > > > > ?column? 
> > > > > > > > ----------
> > > > > > > >    t
> > > > > > > >    (1 row)
> > 
> > If you think of "NaN" literally as "not a number", then FALSE would
> > make sense, since "not a number" implies "not a number between 0 and 1".
> > But since NaN is the result of operations like 0/0 or infinity - infinity,
> > NULL might be better.
> > So I'd opt for NULL too.
> 
> Thanks.  Do you think it's acceptable that returning false instead of
> NULL as an alternative behavior?

Yes, I think that is acceptable.

Yours,
Laurenz Albe




pgsql-hackers by date:

Previous
From: Kyotaro Horiguchi
Date:
Subject: Re: Issue with point_ops and NaN
Next
From: Arseny Sher
Date:
Subject: Re: Flaky vacuum truncate test in reloptions.sql