Help save net neutrality! Learn more.
Close

#2 Incorrect transaction boundaries

open
nobody
None
9
2009-02-27
2009-02-27
Roy Hann
No

The Stock-Level transaction and the Order-Status transaction are both missing a call to the transCommit()
method.

Need to add a call to transCommit() at lines 696 and 1149 of jTPCCTerminal.java .

Discussion

  • Roy Hann

    Roy Hann - 2009-02-27
    • priority: 5 --> 9
     
  • Daniel

    Daniel - 2012-02-09

    These transactions only read data and never update data. Commit only needs to be called when updating data.

     
  • Roy Hann

    Roy Hann - 2012-02-09

    I disagree. Reading data starts a transaction implicitly, meaning that the session is entitled to read consistency until it explicitly ends the transaction. Some DBMSs ensure read consistency using pessimistic locking. If a session that no longer requires read consistency fails to commit then the the lock is held and blocks writers. (DBMSs that use MVCC or optimistic locking won't notice that the transaction is being needlessly prolonged.) On the basis that the benchmark attempts to be DBMS agnostic it must commit as soon as read consistency is no longer required regardless of whether there has been an update.

     

Log in to post a comment.