[SERVER-65262] Expand usage of WT numerical timestamp API Created: 05/Apr/22 Updated: 29/Oct/23 Resolved: 03/May/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.0.1, 4.4.16, 5.0.11, 6.1.0-rc0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Gregory Noma | Assignee: | Gregory Noma |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||
| Backport Requested: |
v6.0, v5.0, v4.4
|
||||||||||||||||||||
| Sprint: | Execution Team 2022-05-16 | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Description |
|
In One option is to call timestamp_transaction_uint twice before commit_transaction, something like:
A potential downside is that there may be some extra overhead from this approach, since the timestamps will be validated twice: once when set and once when committing. Another option is to look into adding a new interface from the WT side for this purpose. |
| Comments |
| Comment by Githook User [ 26/Jul/22 ] |
|
Author: {'name': 'Gregory Noma', 'email': 'gregory.noma@gmail.com', 'username': 'gregorynoma'}Message: (cherry picked from commit 497bbb6faf83673f226a34988e0d75ad62e2020d) |
| Comment by Githook User [ 25/Jul/22 ] |
|
Author: {'name': 'Gregory Noma', 'email': 'gregory.noma@gmail.com', 'username': 'gregorynoma'}Message: (cherry picked from commit 497bbb6faf83673f226a34988e0d75ad62e2020d) |
| Comment by Githook User [ 25/Jul/22 ] |
|
Author: {'name': 'Gregory Noma', 'email': 'gregory.noma@gmail.com', 'username': 'gregorynoma'}Message: (cherry picked from commit 497bbb6faf83673f226a34988e0d75ad62e2020d) |
| Comment by Githook User [ 03/May/22 ] |
|
Author: {'name': 'Gregory Noma', 'email': 'gregory.noma@gmail.com', 'username': 'gregorynoma'}Message: |