There is nothing to prevent a user from calling WT_SESSION::timestamp_transaction on a non-running transaction. That will add the non-running transaction to the commit_timestampq. Is there any reason to allow this? It can lead to subtle bugs in the user code.
Don't allow setting a commit timestamp on a non-running transaction
- Assignee:
- 
    
            
            
    Susan LoVerso (Inactive) 
- Reporter:
- 
    
            
            
    Susan LoVerso (Inactive) 
- Votes:
- 
                    0 Vote for this issue
- Watchers:
- 
                    
                    
                    4 Start watching this issue
- Created:
- Updated:
- Resolved: