YugabyteDB has introduced a new innovation called Wait-on-Conflict with Read Committed Isolation, which provides the same behavior as Read Committed for standard PostgreSQL but in a distributed environment. This feature allows transactions to wait until all conflicting transactions have finished before making progress or aborting, providing a more predictable and resilient experience for applications. The new feature is enabled by setting the YB-TServer gflag enable_wait_queues=true and can be used with a timeout value to provide a window of time for other application operations to complete. YugabyteDB has tested this feature in two deployment scenarios and found that it delivers smooth, predictable P99 latency and excellent throughput performance, making it easier for users to "lift-and-shift" applications from PostgreSQL to a modern, distributed database like YugabyteDB.