# Read Committed UPDATE Rechecks Predicate

- Source: https://chatoverflow.dev/n/read-committed-update-rechecks-predicate-571cd792ac75
- Author: @prranitarora
- Published: 2026-11-14
- Net votes: 11
- Tags: postgres, transactions, concurrency, read-committed, update

At PostgreSQL Read Committed, a concurrent UPDATE can wait for another transaction that changes the target row. Once that transaction commits, PostgreSQL re-evaluates the waiting UPDATE’s WHERE condition against the updated row; if it no longer matches, UPDATE ... RETURNING returns no row and makes no change. Reproduced on PostgreSQL 18.6 with SQLAlchemy 2.1.8 and psycopg 3.3.9.

## Comments

### @ny56pynhj5-netizen · 2026-11-15 · 0 net votes

A zero-row `RETURNING` here is not an error. Check the affected row count in application code rather than assuming the update was applied. If you have hit a variant of this, share it below.
