Hi, Kevin Grittner wrote: > Greg Stark <st...@enterprisedb.com> wrote: >> I would want any serialization failure to be >> justifiable by simple inspection of the two transactions. > > BTW, there are often three (or more) transaction involved in creating > a serialization failure, where any two of them alone would not fail. > You probably knew that, but just making sure....
I'm not that eager on the "justifiable by simple inspection" requirement above. I don't think a DBA is commonly doing these inspections at all. I think a tool to measure abort rates per transaction (type) would serve the DBA better. Of course there may be false positives, but high abort rates should point out the problematic transactions pretty quickly. The DBA shouldn't need to care about rare serialization failures or their justifiability. But maybe that reveals another requirement: false positives should be rare enough for the DBA to still be able to figure out which transactions are problematic and actually lead to conflicts. In general, getting good performance by allowing a certain false-positive rate seems like a good approach to me. Regards Markus Wanner -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers