wait_for_commit

In the wait_for_commit method, the next thread’s transaction group is not sent for processing until the previous transaction has processed successfully and the commit is being sent.

This is the default setting. It assumes considerable contention between parallel transactions and results in the staggered execution shown in the figure.

This method maintains transaction serialization by instructing the DSI to wait until a transaction is ready to commit before initiating the next transaction. The next transaction can be submitted to the replicate data server while the first transaction is committing, since the first transaction already holds the locks that it requires.

Thread Timing with the wait_for_commit Serialization Method
Figure 4-6 illustrates the thread timing with wait underscore for underscore commit serialization method. The figure shows three transactions, A, B, and C, where in transaction B is not sent for processing until transaction A has processed successfully and the commit is being sent. Same goes with transaction C, transaction B has to be processed successfully and the commit is being sent.

Figure 4-6 illustrates the thread timing with wait underscore for underscore commit serialization method. The figure shows three transactions, A, B, and C, where in transaction B is not sent for processing until transaction A has processed successfully and the commit is being sent. Same goes with transaction C, transaction B has to be processed successfully and the commit is being sent.