mirror of https://github.com/citusdata/citus.git
44d1f7b950
When an INSERT/SELECT command runs on a distributed table with replication factor >1, we need to ensure that it sees the same result on each placement of a shard. After this change, the router executor takes exclusive locks on shards from which the SELECT in an INSERT/SELECT reads in order to prevent concurrent changes. This is not a very optimal solution, but it's simple and correct. The citus.all_modifications_commutative can be used to avoid aggressive locking. An INSERT/SELECT whose filters are known to exclude any ongoing writes can be marked as commutative. |
||
|---|---|---|
| .. | ||
| distributed | ||
| .gitignore | ||
| citus_config.h.in | ||