From: Tom Lane <tgl@sss.pgh.pa.us>
To: Kyotaro Horiguchi <horikyota.ntt@gmail.com>
cc: bruce@momjian.us, sbjesse@gmail.com, pgsql-hackers@lists.postgresql.org
Subject: Re: Strange behavior with polygon and NaN
In-reply-to: <20200826.172525.155200749215780647.horikyota.ntt@gmail.com>
References: 
 <CAGf+fX70rWFOk5cd00uMfa__0yP+vtQg5ck7c2Onb-Yczp0URA@mail.gmail.com>
 <20200825230350.GA20669@momjian.us>
 <20200826.172525.155200749215780647.horikyota.ntt@gmail.com>
Comments: In-reply-to Kyotaro Horiguchi <horikyota.ntt@gmail.com>
	message dated "Wed, 26 Aug 2020 17:25:25 +0900"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <2811002.1598444329.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Wed, 26 Aug 2020 08:18:49 -0400
Message-ID: <2811003.1598444329@sss.pgh.pa.us>
Precedence: bulk

Kyotaro Horiguchi <horikyota.ntt@gmail.com> writes:
> At Tue, 25 Aug 2020 19:03:50 -0400, Bruce Momjian <bruce@momjian.us> wro=
te in =

>> I can confirm that this two-month old email report still produces
>> different results with indexes on/off in git master, which I don't thin=
k
>> is ever correct behavior.

> I agree to that the behavior is broken. =


Yeah, but ... what is "non broken" in this case?  I'm not convinced
that having point_inside() return zero for any case involving NaN
is going to lead to noticeably saner behavior than today.

			regards, tom lane