mirror of https://github.com/citusdata/citus.git
05fb0dd020
In subquery pushdown, we first ensure that each relation is joined with at least on another relation on the partition keys. That's fine given that the decision is binary: pushdown the query at all or not. With recursive planning, we'd want to check whether any specific part of the query can be pushded down or not. Thus, we need the ability to understand which part(s) of the subquery is safe to pushdown. This commit adds the infrastructure for doing that. |
||
|---|---|---|
| .. | ||
| deparse_shard_query.c | ||
| distributed_planner.c | ||
| insert_select_planner.c | ||
| multi_explain.c | ||
| multi_join_order.c | ||
| multi_logical_optimizer.c | ||
| multi_logical_planner.c | ||
| multi_master_planner.c | ||
| multi_physical_planner.c | ||
| multi_router_planner.c | ||
| postgres_planning_functions.c | ||
| relation_restriction_equivalence.c | ||
| shard_pruning.c | ||