0 votes 0 votes Comment on Statement : When a Transaction rolled back or aborted due to some reason by another transaction,and same transaction wakes up after random time ,It holds new Timestamp. Databases timestamp-ordering + – saxena0612 asked Dec 13, 2017 saxena0612 400 views answer comment Share Follow See all 2 Comments See all 2 2 Comments reply Ashwin Kulkarni commented Dec 13, 2017 reply Follow Share Yes it is true. To make the schedule serializable it may take new timestamp. 0 votes 0 votes Shivansh Gupta commented Dec 13, 2017 reply Follow Share Under what conditions a transaction is rolled back, must be clear in order to comment. Under Basic Timestamp ordering , if a younger transaction performs a conflicting action on a data item which an older tranasction is about to access, then younger transaction is rolled back, and it is restarted with the same timestamp. Suppose there you started giving always new timestamp, then this younger transaction will remain younger to some other transaction and there is a chance that it will get repeatedly rolled back ,i.e., chances of starvation will come. But this is in Basic TO algorithm, if some other algorithm is used, then something else may or may not happen. 0 votes 0 votes Please log in or register to add a comment.