4 ms·
One of the best (or worst) bugs fixed was the aborted transaction for PGsql. I am pretty sure hundreds of Rails developers are battling it every day and don't u
by avitzurel 10y ago
One of the best (or worst) bugs fixed was the aborted transaction for PGsql. I am pretty sure hundreds of Rails developers are battling it every day and don't understand where it's coming from.
Even if you don't upgrade, this is something you should backport using a monkeypatch.
- seanp2k2 10y agoDo you have a link to the bug or the fix? We've seen this in prod for sure.
- Exuma 10y agoCan you explain more what you saw? What fails, and how does it fail? Does it raise an exception and the transaction undoes all queries, or does a query 'half execute' and save a dirty state to the DB?
- faitswulff 10y agoI think that might be a 5.0.0 change, not a 5.0.1 change, if you're referring to: > Restore aborted transaction state when disable_referential_integrity fails due to missing permissions.
- Exuma 10y agoDo you have a link to that?