What happened to the "&&" operator?

Started by Jeff Hoffmannalmost 27 years ago2 messagesgeneral
Jump to latest
#1Jeff Hoffmann
jeff@remapcorp.com

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?

#2Bruce Momjian
bruce@momjian.us
In reply to: Jeff Hoffmann (#1)
Re: [GENERAL] What happened to the "&&" operator?

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