| From: | Aleksander Alekseev <aleksander(at)timescale(dot)com> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Cc: | Colin Caine <cmcaine(at)gmail(dot)com> |
| Subject: | Re: Okay to remove mention of mystery @ and ~ operators? |
| Date: | 2024-04-19 10:08:50 |
| Message-ID: | CAJ7c6TOhz5EwmtJ70_Fo++H0_uxUfkmRfE9O=f3q2Xpkhx+5uw@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
--
Best regards,
Aleksander Alekseev
| From | Date | Subject | |
|---|---|---|---|
| Next Message | shveta malik | 2024-04-19 10:14:38 | Re: Disallow changing slot's failover option in transaction block |
| Previous Message | Aleksander Alekseev | 2024-04-19 09:47:43 | Re: [PATCH] Replace magic constant 3 with NUM_MERGE_MATCH_KINDS |