Re: Bool btree_gin index not chosen on equality contraint, but on greater/lower? - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Bool btree_gin index not chosen on equality contraint, but on greater/lower?
Date
Msg-id 19580.1455468674@sss.pgh.pa.us
Whole thread Raw
In response to Bool btree_gin index not chosen on equality contraint, but on greater/lower?  (Patric Bechtel <patric.bechtel@gmail.com>)
Responses Re: Bool btree_gin index not chosen on equality contraint, but on greater/lower?
List pgsql-hackers
Patric Bechtel <patric.bechtel@gmail.com> writes:
> I tried to add bool support to the btree_gin contrib module, and as far as I can tell, it seems to
> work (wasn't that complicated, actually).
> But now I'm stuck, as PostgreSQL doesn't seem to like to use my new index, if I use equality or
> unequality, just with greater and lower than.

I think your problem is that the planner won't apply
match_boolean_index_clause() or expand_boolean_index_clause(),
because it has a hard-wired idea of which index opclasses could
possibly benefit from that, cf IsBooleanOpfamily().
        regards, tom lane



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: proposal: enhancing slow query log, and autoexplain log about waiting on lock before query exec time
Next
From: Pavel Stehule
Date:
Subject: Re: proposal: enhancing slow query log, and autoexplain log about waiting on lock before query exec time