From: Guillaume Smet <guillaume.smet@gmail.com>
To: Paul Ramsey <pramsey@refractions.net>
Cc: Pg Performance list <pgsql-performance@postgresql.org>
Subject: Re: Proximity query with GIST and row estimation
Date: Wed, 14 Feb 2007 19:12:54 +0100
Message-ID: <1d4e0c10702141012i139feea5q43f8ab3956cfbf09@mail.gmail.com> (raw)
In-Reply-To: <0BD9E842-2DA7-4F90-A732-AFD60C1F50C7@refractions.net>
References: <1d4e0c10702130909g3be0a10fpf2594574c84866c9@mail.gmail.com>
<0BD9E842-2DA7-4F90-A732-AFD60C1F50C7@refractions.net>
Paul,
On 2/14/07, Paul Ramsey <pramsey@refractions.net> wrote:
> You'll find that PostGIS does a pretty good job of selectivity
> estimation.
PostGIS is probably what I'm going to experiment in the future. The
only problem is that it's really big for a very basic need.
With my current method, I don't even have to create a new column: I
create directly a functional index so it's really easy to use.
Using PostGIS requires to create a new column and triggers to maintain
it and install PostGIS of course. That's why it was not my first
choice.
Thanks for your answer.
--
Guillaume
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: guillaume.smet@gmail.com, pramsey@refractions.net
Subject: Re: Proximity query with GIST and row estimation
In-Reply-To: <1d4e0c10702141012i139feea5q43f8ab3956cfbf09@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox