Re: Issue with point_ops and NaN

From: Julien Rouhaud <rjuju123(at)gmail(dot)com>
To: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Issue with point_ops and NaN
Date: 2021-03-30 12:54:41
Message-ID: 20210330125441.kyrjdcktg3vdctqo@nol
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Mar 30, 2021 at 02:47:05PM +0200, Laurenz Albe wrote:
> On Tue, 2021-03-30 at 17:57 +0800, Julien Rouhaud wrote:
> >
> > Getting a consistent behavior shouldn't be hard, but I'm unsure which behavior
> > is actually correct.
>
> I'd say that this is certainly wrong:
>
> SELECT point('NaN','NaN') <@ polygon('(0,0),(1,0),(1,1),(0,0)');
>
> ?column?
> ----------
> t
> (1 row)

Yeah that's what I think too, but I wanted to have confirmation.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message torikoshia 2021-03-30 13:06:58 Re: Get memory contexts of an arbitrary backend process
Previous Message Laurenz Albe 2021-03-30 12:47:05 Re: Issue with point_ops and NaN