This error would almost certainly cause your problem, if you have a version 
from before I fixed it. I would suggest you get the latest cvs version and at 
very least undefine (drop) the <</<&/>>/>& operators and redefine (create) them 
using the definitions in the compiled postgis.sql file. Also you have to re-
create your index. It may be preferable, if possible, to create a whole new 
database using the new postgis (be careful, if you overwrite your old 
libpostgis.so, your old database will be broken) and migrate your data over to 
it - the latest version has Dave's new indexing-prediction histograms in it as 
well.

Chris

Quoting David Blasby <dblasby@refractions.net>:

> Guido Staub wrote:
> 
> > Guido Staub schrieb:
> >
> > > Hi all,
> > >
> > > I'm using one query but using this one with an GiST-index-scan I get
> > > no rows back. Using the same query with an seq scan I get one row
> > > back, as it should be. So, can somebody tell me why I get two
> > > different results?
> 
> There was a bug in the "<&" type operators for GiST - chris committed the
> change to CVS a little while ago.  Perhaps this is whats causing it?
> 
> dave
> ps. I've never used the "<<" or "&>" operators, so they havent been well
> tested.
> 
> 
> _______________________________________________
> postgis-users mailing list
> postgis-users@postgis.refractions.net
> http://postgis.refractions.net/mailman/listinfo/postgis-users
> 
> 




-------------------------------------------------
This mail sent through IMP: http://horde.org/imp/



