From: Tom Lane <tgl@sss.pgh.pa.us>
To: Kyotaro Horiguchi <horikyota.ntt@gmail.com>
Cc: bruce@momjian.us
Cc: sbjesse@gmail.com
Cc: pgsql-hackers@lists.postgresql.org
Subject: Re: Strange behavior with polygon and NaN
Date: Wed, 26 Aug 2020 08:18:49 -0400
Message-ID: <2811003.1598444329@sss.pgh.pa.us> (raw)
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>
Kyotaro Horiguchi <horikyota.ntt@gmail.com> writes:
> At Tue, 25 Aug 2020 19:03:50 -0400, Bruce Momjian <bruce@momjian.us> wrote 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 think
>> 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: tgl@sss.pgh.pa.us, horikyota.ntt@gmail.com, bruce@momjian.us, sbjesse@gmail.com, pgsql-hackers@lists.postgresql.org
Subject: Re: Strange behavior with polygon and NaN
In-Reply-To: <2811003.1598444329@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox