mirror of https://github.com/citusdata/citus.git
65bd540943
DESCRIPTION: Add GUC to control ddl creation behaviour in transactions Historically we would _not_ propagate objects when we are in a transaction block. Creation of distributed tables would not always work in sequential mode, hence objects created in the same transaction as distributing a table that would use the just created object wouldn't work. The benefit was that the user could still benefit from parallelism. Now that the creation of distributed tables is supported in sequential mode it would make sense for users to force transactional consistency of ddl commands for distributed tables. A transaction could switch more aggressively to sequential mode when creating new objects in a transaction. We don't change the default behaviour just yet. Also, many objects would not even propagate their creation when the transaction was already set to sequential, leaving the probability of a self deadlock. The new policy checks solve this discrepancy between objects as well. |
||
|---|---|---|
| .. | ||
| adaptive_executor.c | ||
| citus_custom_scan.c | ||
| directed_acyclic_graph_execution.c | ||
| distributed_execution_locks.c | ||
| distributed_intermediate_results.c | ||
| insert_select_executor.c | ||
| intermediate_results.c | ||
| local_executor.c | ||
| multi_client_executor.c | ||
| multi_executor.c | ||
| multi_server_executor.c | ||
| partitioned_intermediate_results.c | ||
| placement_access.c | ||
| query_stats.c | ||
| repartition_join_execution.c | ||
| subplan_execution.c | ||
| tuple_destination.c | ||