Re: Naming of network_ops vs. inet_ops for SP-GIST
Michael Paquier <michael@paquier.xyz>
From: Michael Paquier <michael@paquier.xyz>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: greenreaper@hotmail.com, pgsql-docs@lists.postgresql.org
Date: 2023-01-25T02:45:22Z
Lists: pgsql-docs
Attachments
- spgist-builtin.patch (text/x-diff) patch
On Tue, Jan 24, 2023 at 03:22:44PM -0500, Tom Lane wrote: > I wonder whether we shouldn't just revert this table to > showing opclass names, and avert our eyes from the theoretical > inconsistency. Michael, looks like it was your 7a1cd5260 > that changed it; what do you think? Yes, the docs should be fixed here. The intention is not to show the operator families but the names of the opclasses. I can only spot one difference in SpGiST for network_ops -> inet_ops as of the report. BRIN, GIN and GiST look to be clean after a second lookup. 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? Anyway, attached is a patch for the docs. Thoughts? -- Michael
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