Re: Supporting = operator in gin/gist_trgm_ops

From: Alexander Korotkov <aekorotkov(at)gmail(dot)com>
To: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>
Cc: Georgios <gkokolatos(at)protonmail(dot)com>, Julien Rouhaud <julien(dot)rouhaud(at)free(dot)fr>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Supporting = operator in gin/gist_trgm_ops
Date: 2020-11-16 06:12:07
Message-ID: CAPpHfdu1te=-VZPZ=fuSSpZcarRxTz9rVcsL6UVBkf4iVQ8ckQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Nov 16, 2020 at 2:13 AM Jeff Janes <jeff(dot)janes(at)gmail(dot)com> wrote:
> On Sat, Nov 14, 2020 at 12:31 AM Alexander Korotkov <aekorotkov(at)gmail(dot)com> wrote:
>> I went through and revised this patch. I made the documentation
>> statement less categorical. pg_trgm gist/gin indexes might have lower
>> performance of equality operator search than B-tree. So, we can't
>> claim the B-tree index is always not needed. Also, simple comparison
>> operators are <, <=, >, >=, and they are not supported.
>
> Is "simple comparison" here a well-known term of art? If I read the doc as committed (which doesn't include the sentence above), and if I didn't already know what it was saying, I would be left wondering which comparisons those are. Could we just say "inequality operators"?

You're right. "Simple comparison" is vague, let's replace it with
"inequality". Pushed, thanks!

------
Regards,
Alexander Korotkov

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Kyotaro Horiguchi 2020-11-16 06:16:36 Re: Strange behavior with polygon and NaN
Previous Message Masahiko Sawada 2020-11-16 05:44:38 Re: Add Information during standby recovery conflicts