Re: [PERFORM] optimizing a geo_distance() proximity query (example and benchmark)

2007-02-06 Thread Merlin Moncure
On 2/6/07, Mark Stosberg <[EMAIL PROTECTED]> wrote: It's also notable that the units used are meters, not miles like geo_distance(). That's what the magic number of "16093.44" is-- 10 miles converted to meters. When I benchmarked this query against the old geo_distance() variation, it was about

Re: [PERFORM] optimizing a geo_distance() proximity query (example and benchmark)

2007-02-05 Thread Bruno Wolff III
On Mon, Feb 05, 2007 at 18:01:05 -0500, Mark Stosberg <[EMAIL PROTECTED]> wrote: > > It's also notable that the units used are meters, not miles like > geo_distance(). That's what the magic number of "16093.44" is-- 10 miles > converted to meters. You can change the earth() function in earthdis

Re: [PERFORM] optimizing a geo_distance() proximity query (example and benchmark)

2007-02-05 Thread Mark Stosberg
Merlin Moncure wrote: > On 2/5/07, Mark Stosberg <[EMAIL PROTECTED]> wrote: >> Bruno Wolff III wrote: >> > On Sat, Feb 03, 2007 at 14:00:26 -0500, >> > Mark Stosberg <[EMAIL PROTECTED]> wrote: >> >> I'm using geo_distance() from contrib/earthdistance would like to >> find a >> >> way to spend up