[Gdal-dev] ogr2ogr segfaults with large SQL statement

[Bruce Raup]

Hello all,

I am experiencing segmentation faults with ogr2ogr when doing a query on a
PostGIS database and converting the result to a shapefile.  It happens when
the query string is very long -- the threshold is somewhere between 2500 and
3500 characters, I think.  I looked through the source code but couldn't
find any statically allocated memory related to that.  Can someone please
give me a hint on how to fix this in the source?  Or could the limit be
greatly extended officially?

I understand that I can use ogr2ogr to *add* records to a shapefile too, so
I think I can call ogr2ogr multiple times as a work-around.

Thanks in advance for any input,
Bruce

--
Bruce Raup
http://cires.colorado.edu/~braup/ <http://cires.colorado.edu/%7Ebraup/>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osgeo.org/pipermail/gdal-dev/attachments/20060120/3616a53a/attachment.html