Re: [BUGS] BUG #4967: polygon @> point incorrect for points close to shared borders

2009-08-06 Thread Paul Matthews
Tom Lane wrote: "Paul Matthews" writes: A number of points close to the common border claimed they fell into both of the polygons. How close is "close"? There's some pretty arbitrary fuzzy-comparisons logic in the geometric datatypes ... see

[BUGS] BUG #4967: polygon @> point incorrect for points close to shared borders

2009-08-06 Thread Paul Matthews
The following bug has been logged online: Bug reference: 4967 Logged by: Paul Matthews Email address: p...@netspace.net.au PostgreSQL version: 8.3.7 Operating system: Linux Open Suse 11.0 + 11.1 Description:polygon @> point incorrect for points close to sha

Re: [BUGS] BUG #4810: Complex Contains, Bad Performace.

2009-05-17 Thread Paul Matthews
Tom Lane wrote: "Paul Mathews" 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 gi

[BUGS] BUG #4809: Missing Expected Operator

2009-05-15 Thread Paul Matthews
The following bug has been logged online: Bug reference: 4809 Logged by: Paul Matthews Email address: p...@netspace.net.au PostgreSQL version: 8.3.7 Operating system: Linux OpenSuse 11.0 Description:Missing Expected Operator Details: Not a bug as such, but an