From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
---|---|
To: | Aleksander Alekseev <aleksander(at)timescale(dot)com> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Colin Caine <cmcaine(at)gmail(dot)com> |
Subject: | Re: Okay to remove mention of mystery @ and ~ operators? |
Date: | 2024-04-19 11:49:45 |
Message-ID: | 2CB4FAC8-E4C9-49B4-9926-15D71CBD6D72@yesql.se |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> On 19 Apr 2024, at 12:31, Aleksander Alekseev <aleksander(at)timescale(dot)com> wrote:
>
> Hi,
>
>>> This page says that the `(at)` and `~` operators on various types can be accelerated by a GiST index.
>>>
>>> https://www.postgresql.org/docs/current/gist-builtin-opclasses.html
>>>
>>> These operators have been listed in the file since it was created in 2014, but if they exist then I don't know how to use them or what they do.
>>>
>>> Code examples, for clarity:
>>>
>>>> select box '(0,0),(1, 1)' ~ box '(2,2),(3,3)';
>>> operator does not exist: box ~ box
>>>
>>>> select box '(0,0),(1, 1)' @ box '(2,2),(3,3)';
>>> operator does not exist: box @ box
>>>
>>> If they're a typo or some removed thing then I'd like to remove them from the page. This email is me asking to find out if I'm wrong about that before I try to submit a patch (also very happy for someone with a committer bit to just fix this).
>>
>> Indeed, there is no @(box,box) or ~(box,box) in the \dAo output. These
>> operators were removed by 2f70fdb0644c back in 2020.
>>
>> I will submit a patch for the documentation shortly. Thanks for reporting.
>
> Here is the patch.
Nice catch, and thanks for the patch. I'll apply it with a backpatch to when
they were removed.
--
Daniel Gustafsson
From | Date | Subject | |
---|---|---|---|
Next Message | jian he | 2024-04-19 11:54:43 | Re: documentation structure |
Previous Message | Antonin Houska | 2024-04-19 11:39:18 | Re: UniqueKey v2 |