mirror of https://github.com/citusdata/citus.git
6f381443a9
This commit applies the logic that exists in INSERT .. SELECT
planning to the subquery pushdown changes.
The main algorithm is followed as :
- pick an anchor relation (i.e., target relation)
- per each target shard interval
- add the target shard interval's shard range
as a restriction to the relations (if all relations
joined on the partition keys)
- Check whether the query is router plannable per
target shard interval.
- If router plannable, create a task
|
||
|---|---|---|
| .. | ||
| multi_agg_distinct.source | ||
| multi_agg_type_conversion.source | ||
| multi_alter_table_statements.source | ||
| multi_append_table_to_shard.source | ||
| multi_complex_count_distinct.source | ||
| multi_copy.source | ||
| multi_create_schema.source | ||
| multi_insert_select_behavioral_analytics_create_table.source | ||
| multi_large_shardid.source | ||
| multi_load_data.source | ||
| multi_load_large_records.source | ||
| multi_load_more_data.source | ||
| multi_master_delete_protocol.source | ||
| multi_mx_copy_data.source | ||
| multi_outer_join.source | ||
| multi_outer_join_reference.source | ||
| multi_subquery.source | ||
| multi_subquery_0.source | ||
| worker_copy.source | ||