Do you plan to post an updated version of the patch, of what is your response to the points raised last week?
Very sorry about the long delay. I've been in a long trip, no time to look that carefully.
I still haven't made my mind regarding usefulness of range opclasses, so I suggest to split the patch into two parts - 0001 for the opclasses we're confident are useful, and 0002 for those extras. The committer then may apply either 0001 or 0001+0002, depending on his judgment.
I liked the idea. So, follows the patches: - 0001-btree_gin-uuid--base.v2.patch - all types but anyrange, and with the adjustments on comments you proposed
- 0002-btree_gin-uuid--anyrange.v2.patch - adding the anyrange type (must be applied after 0001)