From: Paul Ramsey <pramsey@cleverelephant.ca>
Date: Thu, 21 May 2015 13:12:30 +0000 (+0000)
Subject: Clarify status
X-Git-Tag: 2.2.0rc1~478
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=c5b0c523e01c65b5f4d190bfe05ea9157ed1475e;p=postgis

Clarify status


git-svn-id: http://svn.osgeo.org/postgis/trunk@13536 b70326c6-7e19-0410-871a-916f4a2858ee
---

diff --git a/doc/reference_operator.xml b/doc/reference_operator.xml
index f9979f6e1..303f0f79d 100644
--- a/doc/reference_operator.xml
+++ b/doc/reference_operator.xml
@@ -1104,7 +1104,7 @@ nearest neighbor distance ordering.</para>
 			<note><para>Index only kicks in if one of the geometries is a constant (not in a subquery/cte).  e.g. 'SRID=3005;POINT(1011102 450541)'::geometry instead of a.geom</para></note>
 			<para>Refer to <ulink url="http://workshops.opengeo.org/postgis-intro/knn.html">OpenGeo workshop: Nearest-Neighbour Searching</ulink> for real live example.</para>
 
-			 <para>Availability: 2.2.0 -- True KNN ("K nearest neighbor") only available for PostgreSQL 9.5+</para>
+			 <para>Changed: 2.2.0 -- True KNN ("K nearest neighbor") behavior for PostgreSQL 9.5+</para>
 			 <para>Availability: 2.0.0 -- Weak KNN provides nearest neighbors based on geometry centroid distances instead of true distances. Exact results for points, inexact for all other types. Available for PostgreSQL 9.1+</para>