> This naming was evidently chosen to match btree,
> which has both inet_ops and cidr_ops opclasses
> within its network_ops family.
> spgist only supports inet_ops
FWIW, the documentation for GIST has inet_ops in the equivalent table, so it was extra-confusing because I thought SP-GIST's inconsistency must have a reason - though I see now using '\dAf gist' suggests it's similar.
The index in question was replacing a default btree - we'd started using the table to block by range; when reviewing indexes, I found it wasn't used anymore. (I didn't know btree *had* cidr_ops, but that may be for the best, as it didn't help with 'CIDR contains IP'.)
Best regards,
--Laurence 'GreenReaper' Parry
greenreaper.co.uk - Inkbunny.net
