-
Notifications
You must be signed in to change notification settings - Fork 468
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Document non-blocking transactions #9704
Milestone
Comments
This was referenced Feb 24, 2021
rmloveland
added a commit
that referenced
this issue
Mar 26, 2021
Fixes #9704. See also #9040. Summary of changes: - Add a new section to the 'Transaction Layer' doc: 'Non-blocking transactions', where we provide a high-level overview of the operation and benefits of these types of transactions, followed by some slightly lower-level (but still handwavy) description of how they work.
rmloveland
added a commit
that referenced
this issue
Apr 13, 2021
Fixes #9704. See also #9040. Summary of changes: - Add a new section to the 'Transaction Layer' doc: 'Non-blocking transactions', where we provide a high-level overview of the operation and benefits of these types of transactions, followed by some slightly lower-level (but still handwavy) description of how they work.
rmloveland
added a commit
that referenced
this issue
Apr 20, 2021
Fixes #9704. See also #9040. Summary of changes: - Add a new section to the 'Transaction Layer' doc: 'Non-blocking transactions', where we provide a high-level overview of the operation and benefits of these types of transactions, followed by some slightly lower-level (but still handwavy) description of how they work.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Non-blocking transactions provide the foundation for Multiregion
GLOBAL
tables. They are a variant of CockroachDB's standard read-write transaction protocol that permit low-latency, global reads of read-mostly and read-only (excluding maintenance events) data.See also:
The text was updated successfully, but these errors were encountered: