Richard Guo writes:
> On Fri, Nov 26, 2021 at 5:23 PM Julien Rouhaud wrote:
>> On Fri, Nov 26, 2021 at 2:10 PM Richard Guo
>> wrote:
>>> Seems point_inside() does not handle NaN properly.
>> This is unfortunately a known issue, which was reported twice ([1] and
>> [2]) already. There's a patch
On Fri, Nov 26, 2021 at 5:23 PM Julien Rouhaud wrote:
> Hi,
>
> On Fri, Nov 26, 2021 at 2:10 PM Richard Guo
> wrote:
> >
> > Seems point_inside() does not handle NaN properly.
>
> This is unfortunately a known issue, which was reported twice ([1] and
> [2]) already. There's a patch proposed for
Hi,
On Fri, Nov 26, 2021 at 2:10 PM Richard Guo wrote:
>
> Seems point_inside() does not handle NaN properly.
This is unfortunately a known issue, which was reported twice ([1] and
[2]) already. There's a patch proposed for it:
https://commitfest.postgresql.org/32/2710/ (adding Horiguchi-san in
Here is how it can be reproduced.
create table point_tbl (f1 point);
insert into point_tbl(f1) values ('(5.1, 34.5)');
insert into point_tbl(f1) values (' ( Nan , NaN ) ');
analyze;
create index gpointind on point_tbl using gist (f1);
set enable_seqscan to on;
set enable_indexscan to off;
# sel
