AW: [postgis-users] ST_AsSVG crashes with large/complex geometries

Hugentobler Marco marco.hugentobler at
Thu Feb 19 05:45:53 PST 2009

Hi Mike

It would be helpfull if you could send a sample geometry (maybe directly to me in order to not give advice for easy dos attacks). It may not only be the size but also the complexity or the way a geometry is composed.


-----Ursprüngliche Nachricht-----
Von: postgis-users-bounces at im Auftrag von Mike Leahy
Gesendet: Do 19.02.2009 14:32
An: postgis-users at
Betreff: [postgis-users] ST_AsSVG crashes with large/complex geometries
Hello list,

I'm wondering if anyone has run into issues with st_assvg locking up 
postgresql.  I have an application that generates svg from unioned sets 
of geometries.  So far it has been working pretty well, except I just 
tested it with very large sets of geometries, and it invariably locks up 
the backend database without any errors etc.  I could send a sample 
geometry if that would help, but I think this can probably be done with 
any dataset.  I've verified that the problem is not with st_union, as it 
outputs a geometry just's only when it gets to st_assvg does 
it freeze things...there is no CPU activity.  I do see this in the pg_log:

*** glibc detected *** postgres: postgres testdb [local] SELECT: 
realloc(): invalid next size: 0x000000000220f410 ***

Am I just expecting too much of the st_assvg function, or is this 
something that might be fixable?

Thanks for any advice,
postgis-users mailing list
postgis-users at

More information about the postgis-users mailing list