On Fri, Jul 05, 2013 at 11:24:39AM +0200, Mario Jurcevic wrote: > The is problem, is with the table "Bodenbedeckung__BBNachfuehrung" > which has big polygon inside. > > Without using custom functions the system does not crashes. > > The custom functions wraps the postgis functions. > > Exception is the st_curvetoline and st_linetocurve functions that > during migration of postgis 1.5 to 2.0 were changed. > > Personal opinion: the new behavior is useless.
Uhm, documentation doesn't say anything about the semantic change: http://postgis.net/docs/ST_CurveToLine.html http://postgis.net/docs/ST_LineToCurve.html How did they change ? > We have modified the 2.0 source to include the old st_cur* st_line* > behavior, that seems on 64 bit inside 2.0 source are not working. So this sounds like a bug in your patches, right ? I'll be useful to know more about the semantic change that made you patch those functions. --strk; > Thanks for taking time for looking, > Mario Jurcevic > > > On 07/05/2013 10:08 AM, Sandro Santilli wrote: > >On Thu, Jul 04, 2013 at 09:27:11PM +0200, Mario Jurcevic wrote: > >>Sorry this one is the right: > >> > >> > >>http://ubuntuone.com/202BqXg3Lvtt9zGuu3sDcx > >The SQL file contains calls to custom functions that > >are not available here. I handled to get the import > >started by creating an "import_cadastre" schema, but > >after 2.5k lines of sql the process ends with: > > > >psql:interlis_import_51d5cb94e16e41.40947245.sql:2661: ERROR: function > >geo_curvedtolinear(geometry) does not exist > >LINE 1: ...o_LinearToCurved(ST_Multi(ST_BuildArea(ST_Collect(Geo_Curved... > > > >Can you get the segfault crash without using custom > >functions ? > > > >--strk; _______________________________________________ postgis-users mailing list [email protected] http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users
