Re: Fix picksplit with nan values - Mailing list pgsql-hackers

From Andrew Gierth
Subject Re: Fix picksplit with nan values
Date
Msg-id 87txhl6kc9.fsf@news-spur.riddles.org.uk
Whole thread Raw
In response to Re: Fix picksplit with nan values  (Alexander Korotkov <aekorotkov@gmail.com>)
Responses Re: Fix picksplit with nan values
List pgsql-hackers
>>>>> "Alexander" == Alexander Korotkov <aekorotkov@gmail.com> writes:
Alexander> 2) NaN coordinates should be processed in GiST index scanAlexander> like in sequential scan.

postgres=# select * from pts order by a <-> '(0,0)' limit 10;   a     
----------(1,1)(7,nan)(9,nan)(11,nan)(4,nan)(nan,6)(2,1)(1,2)(2,2)(3,1)
(10 rows)

postgres=# set enable_indexscan=false;
SET

postgres=# select * from pts order by a <-> '(0,0)' limit 10;  a   
-------(1,1)(2,1)(1,2)(2,2)(3,1)(1,3)(3,2)(2,3)(4,1)(1,4)
(10 rows)

this data set was created by:
insert into pts select point(i,j)   from (select generate_series(1,100)::float8 union all select 'nan') s1(i),
(selectgenerate_series(1,100)::float8 union all select 'nan') s2(j)  order by random();
 

-- 
Andrew (irc:RhodiumToad)



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: GUC for data checksums
Next
From: "MauMau"
Date:
Subject: Re: UTF8 national character data type support WIP patch and list of open issues.