From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
---|---|
To: | greenreaper(at)hotmail(dot)com, pgsql-docs(at)lists(dot)postgresql(dot)org, michael(at)paquier(dot)xyz |
Subject: | Re: Naming of network_ops vs. inet_ops for SP-GIST |
Date: | 2023-01-24 20:21:23 |
Message-ID: | CAKFQuwZ6+q9Qs9NNmAJvW1k6bDaALvUv9c++SaHYtRFUG1_EFA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
Michael, please see below:
On Tue, Jan 24, 2023 at 12:44 PM PG Doc comments form <
noreply(at)postgresql(dot)org> wrote:
> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/14/spgist-builtin-opclasses.html
> Description:
>
> I wanted to add an SP-GIST index for an inet field ip_address
>
> In https://www.postgresql.org/docs/14/spgist-builtin-opclasses.html
> network_ops is stated as the built-in opclass for (inet, inet)
> [...]
>
I notice inet_ops, not network_ops, is mentioned in the docs for 13. Perhaps
> it was renamed to network_ops in 15 but not 14?
>
I'm fairly certain this is a simple typo while performing some refactoring
work here:
https://github.com/postgres/postgres/commit/7a1cd5260aa20bc13aec8960a57904b5623d1830
doc/src/sgml/spgist.sgml
L105 + <entry valign="middle"
morerows="10"><literal>network_ops</literal></entry>
L185 - <entry><literal>inet_ops</literal></entry>
David J.
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2023-01-24 20:22:44 | Re: Naming of network_ops vs. inet_ops for SP-GIST |
Previous Message | David G. Johnston | 2023-01-24 20:03:48 | Re: gen_random_uuid is only available with pgcrypto enabled |