~= change

[Paul Ramsey-4]

I'm trying to close tickets (you might have noticed). I broke
http://trac.osgeo.org/postgis/ticket/253 into the "fix" for 1.4 and a
change in behavior http://trac.osgeo.org/postgis/ticket/282 for an
upcoming release. Right now it's mile-stoned at 2.0, but I'd like to
do it in 1.5, because the "fix" returns the old behavior at a
performance cost due to the recheck being applied to all operators on
PgSQL versions < 8.4.

Can I do http://trac.osgeo.org/postgis/ticket/282 for 1.5?

P
_______________________________________________
postgis-devel mailing list
postgis-devel@...
http://postgis.refractions.net/mailman/listinfo/postgis-devel

[Paragon Corporation-2]

+1

-----Original Message-----
From: postgis-devel-bounces@...
[mailto:postgis-devel-bounces@...] On Behalf Of Paul
Ramsey
Sent: Thursday, November 05, 2009 2:48 PM
To: PostGIS Development Discussion
Subject: [postgis-devel] ~= change

I'm trying to close tickets (you might have noticed). I broke
http://trac.osgeo.org/postgis/ticket/253 into the "fix" for 1.4 and a change
in behavior http://trac.osgeo.org/postgis/ticket/282 for an upcoming
release. Right now it's mile-stoned at 2.0, but I'd like to do it in 1.5,
because the "fix" returns the old behavior at a performance cost due to the
recheck being applied to all operators on PgSQL versions < 8.4.

Can I do http://trac.osgeo.org/postgis/ticket/282 for 1.5?

P
_______________________________________________
postgis-devel mailing list
postgis-devel@...
http://postgis.refractions.net/mailman/listinfo/postgis-devel


_______________________________________________
postgis-devel mailing list
postgis-devel@...
http://postgis.refractions.net/mailman/listinfo/postgis-devel

[Kevin Neufeld]

Go right ahead. +1

Paragon Corporation wrote:

> +1
>
> -----Original Message-----
> From: postgis-devel-bounces@...
> [mailto:postgis-devel-bounces@...] On Behalf Of Paul
> Ramsey
> Sent: Thursday, November 05, 2009 2:48 PM
> To: PostGIS Development Discussion
> Subject: [postgis-devel] ~= change
>
> I'm trying to close tickets (you might have noticed). I broke
> http://trac.osgeo.org/postgis/ticket/253 into the "fix" for 1.4 and a change
> in behavior http://trac.osgeo.org/postgis/ticket/282 for an upcoming
> release. Right now it's mile-stoned at 2.0, but I'd like to do it in 1.5,
> because the "fix" returns the old behavior at a performance cost due to the
> recheck being applied to all operators on PgSQL versions < 8.4.
>
> Can I do http://trac.osgeo.org/postgis/ticket/282 for 1.5?
>
> P
> _______________________________________________
> postgis-devel mailing list
> postgis-devel@...
> http://postgis.refractions.net/mailman/listinfo/postgis-devel
>
>
> _______________________________________________
> postgis-devel mailing list
> postgis-devel@...
> http://postgis.refractions.net/mailman/listinfo/postgis-devel

_______________________________________________
postgis-devel mailing list
postgis-devel@...
http://postgis.refractions.net/mailman/listinfo/postgis-devel