K-nearest neighbour search for PostgreSQL by Oleg Bartunov and Teodor Sigaev.
Excellent presentation from PGCon-2010 on the KNN index type in Postgres.
And an exception to the rule about wordy slides.
Or at least wordy slides are better for non-attendees.
KNN uses the <->
distance operator.
And the slides say:
distance operator, should be provided for data type
Looking at the Postgre documentation (9.3, but same for 9.1 and 9.2), I read:
In addition to the typical B-tree search operators,
btree_gist
also provides index support for<>
(“not equals”). This may be useful in combination with an exclusion constraint, as described below.Also, for data types for which there is a natural distance metric,
btree_gist
defines a distance operator<->
, and provides GiST index support for nearest-neighbor searches using this operator. Distance operators are provided forint2
,int4
,int8
,float4
,float8
,timestamp with time zone
,timestamp without time zone
,time without time zone
,date
,interval
,oid
, andmoney
.
What collective subjects would you like to gather up using the defined data types for the distance operator?
How would you represent properties to take advantage of the defined data types?
Are there other data types that you would define for the distance operator?