Re: Simplifying pg_am representation of index sortability

"Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:

> So I'm thinking that the pg_am columns amorderstrategy and amdescorder are
> redundant and should be replaced with a simple boolean, "amcansort" perhaps.
> Any objections?

Any chance of getting rid of the remaining inter-operator relationship columns
in pg_operator? At least for operator with btree strategy numbers oprcom and
oprnegate can be deduced. I think you already got rid of the rest. They are
quite a pain when defining cross-data-type operators.

I guess it's tricky since there may be operators which have valid negators and
commutators but which don't get used by any btree operator class. Does
Postgres actually make use of the oprcom and oprnegate in that case? Could
they be used only for such operators to provide values for when they can't be
automatically deduced?

--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com