Partition tolerance means continuing despite dropped or delayed network messages. It forces distributed systems to trade consistency against availability during partitions, while PACELC adds latency versus consistency when networks are healthy. section 5.5
The multi-master replication trap
Bidirectional PostgreSQL logical replication can look healthy: both nodes display the same tickets. But independent identity generation can assign an existing ID, producing a duplicate-key error. Renaming opened_at on one node then causes the replication worker to stop because the replicated column is missing. High availability therefore requires explicit compromises around consistency, schema coordination, and operational complexity. section 5.5
Figure 5.2 Logical replication in both directions
Use the bidirectional replication diagram to trace how independent PostgreSQL instances exchange changes and where partition-related conflicts can arise. section 5.5

