(Ozgun from Citus) TLDR: We're thinking about multi-shard transactions and we'll share more updates as our timelines become concrete. In the 7.0 release cycle,

(Ozgun from Citus) TLDR: We're thinking about multi-shard transactions and we'll share more updates as our timelines become concrete. In the 7.0 release cycle, we're looking at prototyping work on distributed deadlock detection, a prerequisite for multi-shard transactions. As a quick question, we find that multi-shard transactions fall into multiple categories. Which one did you have in mind? 1. An UPDATE / DELETE over multiple shards 2. BEGIN; tx on one shard from distributed table; tx on another shard; COMMIT 3. BEGIN; tx on distributed table; tx on reference table; COMMIT We currently offer master_modify_multiple_shards() or Postgres' 2PC as potential workarounds, and know that there's definitely more work to be done in this area.