Re: [HACKERS] Re: type coersion (was OR clause status)

> Sounds like if we add the proper pg_am functions for binary
> compatability, the optimizer should then use the proper indexes.
>

I just tried this and it failed. Not sure why yet:

test=> explain select * from test where oid = 3;
NOTICE: QUERY PLAN:

Seq Scan on test (cost=1936.05 size=1 width=8)

EXPLAIN
test=> create index i_test3 on test(oid oidint4ops);
ERROR: DefineIndex: oidint4ops class not found
test=> create index i_test3 on test(oid oidint4_ops);
vacuum ;
CREATE
test=> vacuum ;
VACUUM
test=> explain select * from test where oid = 3;
NOTICE: QUERY PLAN:

Seq Scan on test (cost=1936.05 size=1 width=8)

EXPLAIN

--
Bruce Momjian | 830 Blythe Avenue
maillist(at)candle(dot)pha(dot)pa(dot)us | Drexel Hill, Pennsylvania 19026
+ If your life is a hard drive, | (610) 353-9879(w)
+ Christ can be your backup. | (610) 853-3000(h)