Re: BUG #14032: trigram index is not used for '=' operator

From: Ruslan Zakirov <ruslan(dot)zakirov(at)gmail(dot)com>
To: emre(at)hasegeli(dot)com
Cc: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, Artur Zakirov <a(dot)zakirov(at)postgrespro(dot)ru>, Pg Bugs <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #14032: trigram index is not used for '=' operator
Date: 2016-03-24 15:31:11
Message-ID: CAMOxC8uOb-c71ewhPmXanJRYFtpwgb_dKLj9TaYL6qBpSQ6qCg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Hi,

I all brought up reasonable arguments.

On Thu, Mar 24, 2016 at 6:11 PM, Emre Hasegeli <emre(at)hasegeli(dot)com> wrote:

> It is likely that pg_trgm index created for pattern matching would be
> sufficient for equality for some users. We shouldn't force them to
> create an additional btree index.
>

This lines up with my point of view. I just don't want to create 19 btree
indexes as
long as trigram one is fast enough for my load. Switching to using LIKE in
my case,
good it's not big effort in this situation.

--
Best regards, Ruslan.

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Christian Ullrich 2016-03-24 15:35:23 Re: BUG #13854: SSPI authentication failure: wrong realm name used
Previous Message Robert Haas 2016-03-24 15:30:36 Re: [BUGS] BUG #13854: SSPI authentication failure: wrong realm name used