TransactionRollbackErrors may prevent us to detect real issues

[Ursula Junque]

As seen on today's edge oops summary, we had ~36 TransactionRollbackErrors, for instance OOPS-1313ED736 and OOPS-1313ED459:

TransactionRollbackError: could not serialize access due to concurrent update CONTEXT: SQL statement "SELECT 1 FROM ONLY "public"."branch" x WHERE "id" OPERATOR(pg_catalog.=) $1 FOR SHARE OF x"

and

  TransactionRollbackError: could not serialize access due to concurrent update

According to stub this is expected due to changes he did, but having this much oopses would prevent us to detect if we're having real problems.

[Diogo Matsubara (matsubara)]

Fixed in devel r9139.