Hi all.
I pondered that either, and I also haven't thought about a good use case, but since it has B-Tree support, I thought it should be included on btree_gin as well, so I did.
If you all decide to remove, I'm totally fine with that.
I forgot I have changed that, sorry. I think though that 10.0 was a typo, since it has been introduced way before PostgreSQL 10. But you are right, it should be 1.1.
I can send it later as a bugfix then. Sounds better indeed.
I've just followed what has been done for ENUM type, if we are going to change for range we should also change to use anyenum, no?
Ok.
My English skills aren't very good, so feel free to tweak any comment or documentation I have done ;)
I really appreciate your review. I'd like to know what you think about my comments above.
Thanks a lot.
Best regards,