Skip site navigation (1) Skip section navigation (2)

pgsql: Skip opfamily check in eclass_matches_any_index() when the index

From: tgl(at)postgresql(dot)org (Tom Lane)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Skip opfamily check in eclass_matches_any_index() when the index
Date: 2008-09-12 14:56:13
Message-ID: 20080912145613.9088C7545A3@cvs.postgresql.org (view raw or flat)
Thread:
Lists: pgsql-committers
Log Message:
-----------
Skip opfamily check in eclass_matches_any_index() when the index isn't a
btree.  We can't easily tell whether clauses generated from the equivalence
class could be used with such an index, so just assume that they might be.
This bit of over-optimization prevented use of non-btree indexes for nestloop
inner indexscans, in any case where the join uses an equality operator that
is also a btree operator --- which in particular is typically true for hash
indexes.  Noted while trying to test the current hash index patch.

Modified Files:
--------------
    pgsql/src/backend/optimizer/path:
        indxpath.c (r1.232 -> r1.233)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/optimizer/path/indxpath.c?r1=1.232&r2=1.233)

pgsql-committers by date

Next:From: Tom LaneDate: 2008-09-12 14:56:19
Subject: pgsql: Skip opfamily check in eclass_matches_any_index() when the index
Previous:From: Dave PageDate: 2008-09-12 14:46:05
Subject: stackbuilder - wizard: New icon

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group