Received: from localhost (maia-4.hub.org [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 69E2F9FBD23 for ; Wed, 14 Feb 2007 14:13:08 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-new, port 10024) with ESMTP id 27699-04 for ; Wed, 14 Feb 2007 14:12:58 -0400 (AST) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.4 Received: from wr-out-0506.google.com (wr-out-0506.google.com [64.233.184.229]) by postgresql.org (Postfix) with ESMTP id 444649FBC46 for ; Wed, 14 Feb 2007 14:12:58 -0400 (AST) Received: by wr-out-0506.google.com with SMTP id i21so325434wra for ; Wed, 14 Feb 2007 10:12:55 -0800 (PST) DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=DXbLGRSWB3vkJGTG+q9yml6IImoMoGKvwyA+JXUecv+5NpAv6/CBTQO+HZ3llbq61r9/opgwrsfl8W/pmUKCxHxMSFfAHypvxTLN2ecuR98hYWKpKEdUEBbRqbu6HPY0NnysDtsPUgROZTod+msrocmelwnVUFeOSmuoBeq/65g= Received: by 10.90.52.18 with SMTP id z18mr1016060agz.1171476774957; Wed, 14 Feb 2007 10:12:54 -0800 (PST) Received: by 10.90.113.7 with HTTP; Wed, 14 Feb 2007 10:12:54 -0800 (PST) Message-ID: <1d4e0c10702141012i139feea5q43f8ab3956cfbf09@mail.gmail.com> Date: Wed, 14 Feb 2007 19:12:54 +0100 From: "Guillaume Smet" To: "Paul Ramsey" Subject: Re: Proximity query with GIST and row estimation Cc: "Pg Performance list" In-Reply-To: <0BD9E842-2DA7-4F90-A732-AFD60C1F50C7@refractions.net> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <1d4e0c10702130909g3be0a10fpf2594574c84866c9@mail.gmail.com> <0BD9E842-2DA7-4F90-A732-AFD60C1F50C7@refractions.net> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200702/156 X-Sequence-Number: 23210 Paul, On 2/14/07, Paul Ramsey 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