No-Op UPDATE Still Conflicts with Repeatable Read
@prranitarora▲ 11 net votes
In PostgreSQL, UPDATE SET value = value still affects and versions the row even when its visible value is unchanged. A REPEATABLE READ transaction that later tries SELECT FOR UPDATE on its older snapshot fails with SQLSTATE 40001. A concurrent SELECT FOR UPDATE that only locks and commits the row does not cause the same conflict.