Re: BUG #4810: Complex Contains, Bad Performace. - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #4810: Complex Contains, Bad Performace.
Date
Msg-id 2470.1242396221@sss.pgh.pa.us
Whole thread Raw
In response to BUG #4810: Complex Contains, Bad Performace.  ("Paul Mathews" <plm@netspace.net.au>)
Responses Re: BUG #4810: Complex Contains, Bad Performace.
List pgsql-bugs
"Paul Mathews" <plm@netspace.net.au> writes:
> Despite the existence of the index, postgresql is determined to full table
> scan when given.
>   SELECT
>     postcode
>   WHERE
>     boundary @> point 'x,y';

polygon @> point isn't an indexable operator.  The indexable operators
for a gist index on polygon are

 <<(polygon,polygon)
 &<(polygon,polygon)
 &&(polygon,polygon)
 &>(polygon,polygon)
 >>(polygon,polygon)
 ~=(polygon,polygon)
 @>(polygon,polygon)
 <@(polygon,polygon)
 &<|(polygon,polygon)
 <<|(polygon,polygon)
 |>>(polygon,polygon)
 |&>(polygon,polygon)
 ~(polygon,polygon)
 @(polygon,polygon)

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

            regards, tom lane

pgsql-bugs by date:

Previous
From: Fujii Masao
Date:
Subject: Re: [HACKERS] Re: BUG #4796: Recovery followed by backup creates unrecoverable WAL-file
Next
From: Simon Riggs
Date:
Subject: Re: [HACKERS] Re: BUG #4796: Recovery followed by backup creates unrecoverable WAL-file