[postgis-devel] PostGIS 1.4 RC1 vote

Paragon Corporation lr at pcorp.us
Mon Jun 29 12:41:58 PDT 2009

I really think the 212 can wait.  Its something that isn't even documented.
That can really wait till 1.4.1.  Remember we have a 1.4.1 and this would be
a bug fix so can fit nicely in there.

I feel kind of the same about 210 (since I'm pretty sure we've had this
problem for a really long time -- it might have been a change in PostgreSQL
or something else that makes this more apparent thought).  Though 210 is
more of a serious issue since it does cause crashes under unpredicatable
circumstances especially in 64-bit.



-----Original Message-----
From: postgis-devel-bounces at postgis.refractions.net
[mailto:postgis-devel-bounces at postgis.refractions.net] On Behalf Of Mark
Sent: Monday, June 29, 2009 10:23 AM
To: PostGIS Development Discussion
Subject: Re: [postgis-devel] PostGIS 1.4 RC1 vote

Paul Ramsey wrote:

> I think we need this patch on 1.4 before we do the RC.
> http://trac.osgeo.org/postgis/ticket/210

Yeah, I agree - it's the only bug report we've had against 1.4 so far, and
the reporter has done a good job with debug logs etc. so it would be nice to
get this one resolved before release. If anyone can help out with testing,
please do.

I also think that we need to solve part of #212; not so much the interaction
with other functions, but we need to get a point where a user can at least
pull out the same geometry that they put in without crashing before a

Mark L, are you able to try and resolve this over the next few days?



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

More information about the postgis-devel mailing list