Skip site navigation (1) Skip section navigation (2)

Re: BUG #4810: Complex Contains, Bad Performace.

From: Paul Matthews <plm(at)netspace(dot)net(dot)au>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #4810: Complex Contains, Bad Performace.
Date: 2009-05-17 10:36:19
Message-ID: (view raw or whole thread)
Lists: pgsql-bugs
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<body bgcolor="#ffffff" text="#000000">
Tom Lane wrote:
<blockquote cite="mid:2470(dot)1242396221(at)sss(dot)pgh(dot)pa(dot)us" type="cite">
  <pre wrap="">"Paul Mathews" <a class="moz-txt-link-rfc2396E" href="mailto:plm(at)netspace(dot)net(dot)au">&lt;plm(at)netspace(dot)net(dot)au&gt;</a> writes:
  <blockquote type="cite">
    <pre wrap="">Despite the existence of the index, postgresql is determined to full table
scan when given.
    boundary @&gt; point 'x,y';
  <pre wrap=""><!---->
polygon @&gt; point isn't an indexable operator.  The indexable operators
for a gist index on polygon are


So it looks like you need to convert the point to a one-point polygon.

			regards, tom lane

&nbsp;&nbsp; g.boundary @&gt; polygon(box(w.geocode,w.geocode));<br>
Is there are more convenient, less ugly, way to convert a point to a

Attachment: unknown_filename
Description: text/html (1.4 KB)

In response to

pgsql-bugs by date

Next:From: Helena BianderDate: 2009-05-17 15:56:51
Subject: BUG #4813: Database can not be initialized
Previous:From: Dave PageDate: 2009-05-17 09:13:40
Subject: Re: Perl 5.10 vs. PG 8.4 on Win32

Privacy Policy | About PostgreSQL
Copyright © 1996-2015 The PostgreSQL Global Development Group