aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gistutil.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2011-10-26 17:52:02 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2011-10-26 17:52:29 -0400
commit3e4b3465b6345b75659e8f897976d4c810408762 (patch)
tree926411ab20e56c663b9793568577a2f73bc3bed8 /src/backend/access/gist/gistutil.c
parent360429e1d17947c17659cd57dbaaba5c10fcbd6a (diff)
downloadpostgresql-3e4b3465b6345b75659e8f897976d4c810408762.tar.gz
postgresql-3e4b3465b6345b75659e8f897976d4c810408762.zip
Improve planner's ability to recognize cases where an IN's RHS is unique.
If the right-hand side of a semijoin is unique, then we can treat it like a normal join (or another way to say that is: we don't need to explicitly unique-ify the data before doing it as a normal join). We were recognizing such cases when the RHS was a sub-query with appropriate DISTINCT or GROUP BY decoration, but there's another way: if the RHS is a plain relation with unique indexes, we can check if any of the indexes prove the output is unique. Most of the infrastructure for that was there already in the join removal code, though I had to rearrange it a bit. Per reflection about a recent example in pgsql-performance.
Diffstat (limited to 'src/backend/access/gist/gistutil.c')
0 files changed, 0 insertions, 0 deletions