Tom Lane wrote: > Given that we only allow one default opclass for a datatype regardless > of schema (see DefineOpClass), it's not really necessary for > GetDefaultOpClass to restrict its search. I can think of some corner > cases involving multiple binary-compatible-datatype matches where the > restriction might give a unique answer when an unrestricted search would > not, but I kinda doubt this would ever arise in practice.
How about doing the constrained search first, and revert to the unconstrained behavior if it doesn't find the desired opclass? -- Alvaro Herrera http://www.CommandPrompt.com/ PostgreSQL Replication, Consulting, Custom Development, 24x7 support ---------------------------(end of broadcast)--------------------------- TIP 2: Don't 'kill -9' the postmaster
