> At every commit, you need handle the possibility of a serialization exception and retry the transaction. Yeah, but it seems so strange to me. Imagine if a da

> At every commit, you need handle the possibility of a serialization exception and retry the transaction. Yeah, but it seems so strange to me. Imagine if a database simply executed all transactions serially. Then there would be no serialization anomalies (though it would be slow, yada yada). So it seems serializable isolation presents a facade of serial execution, but only like, half a facade. You have to deal with the leak in the abstraction yourself and it's surprising to everyone who hears about it for the first time. I wonder why this choice was made.