Re: Naming of network_ops vs. inet_ops for SP-GIST
Laurence Parry <greenreaper@hotmail.com>
From: Laurence Parry <greenreaper@hotmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: "pgsql-docs@lists.postgresql.org" <pgsql-docs@lists.postgresql.org>, Michael Paquier <michael@paquier.xyz>
Date: 2023-01-24T21:34:32Z
Lists: pgsql-docs
> 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. https://www.postgresql.org/docs/14/gist-builtin-opclasses.html 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
Commits
-
doc: Fix network_ops -> inet_ops in SpGiST operator class list
- e9774151c278 14.7 landed
- 88c27b8fe201 15.2 landed
- d7c4830abb18 16.0 landed
-
doc: Rework tables for built-in operator classes of index AMs
- 7a1cd5260aa2 14.0 cited