Michael Paquier <michael@paquier.xyz> writes:
> I don't have a strong opinion about the naming inconsistency between
> the opclass name and the opfamily name in this case, though, couldn't
> it create more problems than actually fix something?
Well, it's been like that from day one and people haven't complained.
I think changing it now would add more confusion than it subtracts.
> Anyway, attached is a patch for the docs. Thoughts?
Works for me.
regards, tom lane