< Back to blog home Fujitsu PostgreSQL blog

Detection and resolution of conflicts in PostgreSQL logical replication

Ajin Cherian | July 15, 2025

We showed how PostgreSQL detects and resolves conflicts in logical replication, highlighting upcoming enhancements in PostgreSQL 18 aimed at enabling automated and user-defined conflict resolution.

Let's dive into the topic

Below, you'll find the slides from our presentation at PGConf.dev 2025.

Side by sideClick to view the slides side by side

Top to bottomClick to view the slides in vertical orientation

The wrap-up

Participating in PGConf.dev was a fantastic opportunity to connect with the vibrant PostgreSQL community and share ideas that will shape the future of the ecosystem. Representing Fujitsu alongside Zhijie Hou, we had the privilege of co-presenting on a topic that’s becoming increasingly critical in modern database architectures—conflict detection and resolution in logical replication.

Our talk explored the evolution of conflict handling in PostgreSQL, from the manual and error-prone processes of earlier versions to the more robust and user-friendly features introduced in PostgreSQL 15, and the exciting enhancements coming in PostgreSQL 18.

We showcased real-world examples, new conflict types, and upcoming features like automatic conflict resolution and dead tuple retention, all aimed at making logical replication more resilient and easier to manage. It was an honor to contribute to the ongoing conversation about high-availability and multi-node replication strategies in PostgreSQL.