Tom Lane wrote:
> BTW, it might be better for array_cmp to insist that the array element
> type have a default btree opclass, and use the comparison proc from that
> opclass in place of equality_oper() and ordering_oper(). This'd be
> faster (only one call per comparison) as well as more semantically pure.
Sounds like a good idea. Should I work this now, or wait for more comments?
> I've got some other problems with this patch (I still don't understand
> what the hacking on aggregates is supposed to accomplish, for example)
The aggregates hacking was a bit convoluted by the desire to support
polymorphic aggregates using polymorphic functions. You end up with many
possible states, some of which are invalid because they don't provide
enough context to resolve the polymorphic types. Any suggestions?
Joe
