]> granicus.if.org Git - postgresql/commit
Phase 2 of project to make index operator lossiness be determined at runtime
authorTom Lane <tgl@sss.pgh.pa.us>
Sun, 13 Apr 2008 19:18:14 +0000 (19:18 +0000)
committerTom Lane <tgl@sss.pgh.pa.us>
Sun, 13 Apr 2008 19:18:14 +0000 (19:18 +0000)
commit24558da14a26337e945732d3b435b07edcbb6733
tree7a6fbd12b1793e46d4584f49a1bc9373300125d8
parentc22ed3d523782c43836c163c16fa5a7bb3912826
Phase 2 of project to make index operator lossiness be determined at runtime
instead of plan time.  Extend the amgettuple API so that the index AM returns
a boolean indicating whether the indexquals need to be rechecked, and make
that rechecking happen in nodeIndexscan.c (currently the only place where
it's expected to be needed; other callers of index_getnext are just erroring
out for now).  For the moment, GIN and GIST have stub logic that just always
sets the recheck flag to TRUE --- I'm hoping to get Teodor to handle pushing
that control down to the opclass consistent() functions.  The planner no
longer pays any attention to amopreqcheck, and that catalog column will go
away in due course.
doc/src/sgml/indexam.sgml
src/backend/access/gin/ginget.c
src/backend/access/gist/gistget.c
src/backend/access/hash/hash.c
src/backend/access/index/genam.c
src/backend/access/index/indexam.c
src/backend/access/nbtree/nbtree.c
src/backend/commands/cluster.c
src/backend/executor/nodeIndexscan.c
src/backend/optimizer/plan/createplan.c
src/include/access/relscan.h