y
for concurrency.
But what else if there is no way of knowing what the slow transaction
conflicts against.
As things with concurrency involved have a tendency to pop up in production
and not in test I think it is important to
start thinking about them as soon as possible.
Best Regards
Dan S
f, take an explicit lock on and so on to reduce
serialization failure rate.
If holding a list of the involved transactions turns out to be expensive,
maybe one should be able to turn it on by a GUC only when you have a problem
and need the extra information to track it down.
Best Regards
Dan S
2010/
Hi !
I wonder if the SSI implementation will give some way of detecting the cause
of a serialization failure.
Something like the deadlock detection maybe where you get the sql-statements
involved.
Best Regards
Dan S
