Jerry,
So far you're the only one to report issues w/ the core functions.
Both _ST_DistanceTreea and _ST_DistanceUncached have worked for folks
who ran into the caching problem. And as I noted, _ST_DistanceUncached
is the old 2.0 logic. So I'd very much like to hear more about issues
w/ _ST_Distanc
On Tue, Feb 04, 2014 at 08:22:18AM -0800, Jerry Sievert wrote:
> and decided to stay with 2.0.4 for the time being, patching it to
> work with PG9.3. 2.0.x has been rock solid for us, and has worked very
> well for our use case.
Speaking of which.. maybe we should push 2.0.5 out.
It's full of bu
Paul,
Agreed. I suspect that this was masking another, more subtle issue in 2.1.
And I can confirm that 2.0.x has been working as designed. We've been
running it for just over a year at this point, and have yet to see the
random failures that I reported with the brute force change in 2.1. We m
Hey, if your data range from 60 000 to 600 000, you can do a translation
"-300 000" but it won't help you much,
but there is no miracle,
you can't get precise result with very big coordinates (you may need to
divide to reduce precision. eg. divide by 100 and round to 0.001, so you
would get a preci
