[postgis-devel] PostGIS 1.5 regression with GEOS 3.0.3

[Paragon Corporation]

Mark,

It only became apparent with PostGIS 1.4.  People started to stress test the
cascaded union feature and ran into all sorts of topological erros.

The quick fix was to have them upgrade to gEOS 3.2 which didn't exhibit the
behavior.

Also I think the issues people may be seeing between windows and linux, may
be different versions  of GEOS  even though they both say 3.1.0.

We compiled GEOS from the tar ball, but before the GEOS versions in trunk
did not change until release, which means people running trunk versions of
3.2 would register as 3.1.0.  Paul changed that  policy recently to bump the
release number as soon as it was released.

Thanks,
Regina 

-----Original Message-----
From: postgis-devel-bounces at postgis.refractions.net
[mailto:postgis-devel-bounces at postgis.refractions.net] On Behalf Of Mark
Cave-Ayland
Sent: Friday, January 15, 2010 10:41 AM
To: PostGIS Development Discussion
Subject: Re: [postgis-devel] PostGIS 1.5 regression with GEOS 3.0.3

Paragon Corporation wrote:

> I see it as
> 
> 3.0 - has known bugs
> 3.1 - works well, but can leak memory, has more topological 
> exceptions, doesn't support all PostGIS 1.5 function (some will be 
> disabled IFDEF
> madness)
> 3.2 - (hopefully) works well with no memory leaks
> 
> Not that it matters though.
> 
> Thanks,
> Regina

Do you really find that 3.1 is worse than 3.0 for topological exceptions?
Wow, I'm obviously not stressing it enough...


ATB,

Mark.

-- 
Mark Cave-Ayland - Senior Technical Architect
PostgreSQL - PostGIS
Sirius Corporation plc - control through freedom
http://www.siriusit.co.uk
t: +44 870 608 0063

Sirius Labs: http://www.siriusit.co.uk/labs
_______________________________________________
postgis-devel mailing list
postgis-devel at postgis.refractions.net
http://postgis.refractions.net/mailman/listinfo/postgis-devel