[postgis-devel] Issue 95 in postgis: PostGIS 1.4 documentation update

[codesite-noreply at google.com]

Comment #13 on issue 95 by mark.cav... at siriusit.co.uk: PostGIS 1.4  
documentation update
http://code.google.com/p/postgis/issues/detail?id=95

Hi Kevin.

Remember that only && has a selectivity function that will be anywhere  
meaningful.
Just because an operator is indexable, doesn't mean that the planner *has*  
to use it.
What happens if you do a "SET enable_seqscan = 'f'" before trying your  
query?


ATB,

Mark.


--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings