diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2005-06-13 23:14:49 +0000 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2005-06-13 23:14:49 +0000 |
| commit | c186c93148fdfa5a39972331318eda5318ff5eba (patch) | |
| tree | 31195d72e9b44d701eaa9018e498145f3d46f929 /src/backend/access/index | |
| parent | 077811605e07212139c3df503fdaa081690635ca (diff) | |
Change the planner to allow indexscan qualification clauses to use
nonconsecutive columns of a multicolumn index, as per discussion around
mid-May (pghackers thread "Best way to scan on-disk bitmaps"). This
turns out to require only minimal changes in btree, and so far as I can
see none at all in GiST. btcostestimate did need some work, but its
original assumption that index selectivity == heap selectivity was
quite bogus even before this.
Diffstat (limited to 'src/backend/access/index')
| -rw-r--r-- | src/backend/access/index/indexam.c | 24 |
1 files changed, 1 insertions, 23 deletions
diff --git a/src/backend/access/index/indexam.c b/src/backend/access/index/indexam.c index 81c2114976e..a445efc7154 100644 --- a/src/backend/access/index/indexam.c +++ b/src/backend/access/index/indexam.c @@ -8,7 +8,7 @@ * * * IDENTIFICATION - * $PostgreSQL: pgsql/src/backend/access/index/indexam.c,v 1.82 2005/05/27 23:31:20 tgl Exp $ + * $PostgreSQL: pgsql/src/backend/access/index/indexam.c,v 1.83 2005/06/13 23:14:48 tgl Exp $ * * INTERFACE ROUTINES * index_open - open an index relation by relation OID @@ -25,7 +25,6 @@ * index_getmulti - get multiple tuples from a scan * index_bulk_delete - bulk deletion of index tuples * index_vacuum_cleanup - post-deletion cleanup of an index - * index_cost_estimator - fetch amcostestimate procedure OID * index_getprocid - get a support procedure OID * index_getprocinfo - get a support procedure's lookup info * @@ -719,27 +718,6 @@ index_vacuum_cleanup(Relation indexRelation, } /* ---------------- - * index_cost_estimator - * - * Fetch the amcostestimate procedure OID for an index. - * - * We could combine fetching and calling the procedure, - * as index_insert does for example; but that would require - * importing a bunch of planner/optimizer stuff into this file. - * ---------------- - */ -RegProcedure -index_cost_estimator(Relation indexRelation) -{ - FmgrInfo *procedure; - - RELATION_CHECKS; - GET_REL_PROCEDURE(amcostestimate); - - return procedure->fn_oid; -} - -/* ---------------- * index_getprocid * * Some indexed access methods may require support routines that are |