Don't deep clone POINTARRAY in GML input routine.

Let's see if doing so exposes more memory errors (#1591).
Does run valgrind clean here.

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

diff --git a/postgis/lwgeom_in_gml.c b/postgis/lwgeom_in_gml.c
index 0d8ce77e166da38f60056604bce25bd9d5bfcf38..1a045b6e741f4d3ea5481b22c5a8d2e9d975cccf 100644 (file)
--- a/postgis/lwgeom_in_gml.c
+++ b/postgis/lwgeom_in_gml.c
@@ -618,9 +618,7 @@ static POINTARRAY* parse_gml_coordinates(xmlNodePtr xnode, bool *hasz)
 
        xmlFree(gml_coord);
 
-       /* TODO: this makes no sense, we shouldn't have to clone. but we're seeing 
-          memory problems when we don't. */
-       return ptarray_clone_deep(dpa);
+       return dpa; /* ptarray_clone_deep(dpa); */
 }