Re: BUG #14032: trigram index is not used for '=' operator - Mailing list pgsql-bugs

From Ruslan Zakirov
Subject Re: BUG #14032: trigram index is not used for '=' operator
Date
Msg-id CAMOxC8uOb-c71ewhPmXanJRYFtpwgb_dKLj9TaYL6qBpSQ6qCg@mail.gmail.com
Whole thread Raw
In response to Re: BUG #14032: trigram index is not used for '=' operator  (Emre Hasegeli <emre@hasegeli.com>)
List pgsql-bugs
Hi,

I all brought up reasonable arguments.

On Thu, Mar 24, 2016 at 6:11 PM, Emre Hasegeli <emre@hasegeli.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.

pgsql-bugs by date:

Previous
From: srivathson.k@zohocorp.com
Date:
Subject: BUG #14047: Problem while initdb - 0xC000001D
Next
From: josnyder@yelp.com
Date:
Subject: BUG #14044: Queries immediately conflict with recovery when recovery_min_apply_delay is used