Thread

1. What happened to the "&&" operator?

   Jeff Hoffmann <jeff@remapcorp.com> — 1999-06-18T14:51:35Z

   I'm just installing 6.5 and I did a dump/restore of a database that I
   had in 6.4.2.  This database has a field with a box type which is
   indexed with an r-tree index.  The dump/restore went OK, but when I
   tried to run a query against it, I got a weird error:
   
   ERROR:  Operator 500 must have a restriction selectivity estimator to be
   used in a btree index
   
   This may not seem like a weird error to some, but why am I getting a
   b-tree error on an r-tree index?
   Anybody know anything about this?
   
   

2. Re: [GENERAL] What happened to the "&&" operator?

   Bruce Momjian <maillist@candle.pha.pa.us> — 1999-07-08T00:36:32Z

   FYI, this will be fixed in 6.5.
   
   
   > I'm just installing 6.5 and I did a dump/restore of a database that I
   > had in 6.4.2.  This database has a field with a box type which is
   > indexed with an r-tree index.  The dump/restore went OK, but when I
   > tried to run a query against it, I got a weird error:
   > 
   > ERROR:  Operator 500 must have a restriction selectivity estimator to be
   > used in a btree index
   > 
   > This may not seem like a weird error to some, but why am I getting a
   > b-tree error on an r-tree index?
   > Anybody know anything about this?
   > 
   > 
   
   
   -- 
     Bruce Momjian                        |  http://www.op.net/~candle
     maillist@candle.pha.pa.us            |  (610) 853-3000
     +  If your life is a hard drive,     |  830 Blythe Avenue
     +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026