| From: | Bruno Wolff III <bruno(at)wolff(dot)to> |
|---|---|
| To: | Mark Stosberg <mark(at)summersault(dot)com> |
| Cc: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: optimizing a geo_distance() proximity query |
| Date: | 2007-02-05 20:22:09 |
| Message-ID: | 20070205202209.GA20382@wolff.to |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Mon, Feb 05, 2007 at 14:47:25 -0500,
Mark Stosberg <mark(at)summersault(dot)com> wrote:
>
> This is also interesting. Is this approach practical if I want to index
> what's near each of about 40,000 US zipcodes, or the approach mostly
> useful if you there are just a small number of fixed points to address?
I think the answer depends on what your data model is. If you treat each
zip code as having a location at a single point, the earth distance stuff
should work. If you are trying to include the shape of each zip code in
your model and measure distances to the nearest point of zip codes, then
you will probably be better off using postgis.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mark Stosberg | 2007-02-05 23:01:05 | Re: optimizing a geo_distance() proximity query (example and benchmark) |
| Previous Message | Merlin Moncure | 2007-02-05 20:15:15 | Re: optimizing a geo_distance() proximity query |