[docs] Update documentation for Wait-on-Conflict concurrency control #13894
Assignees
Labels
area/documentation
Documentation needed
temp/docs-migration
TEMPORARY USE for migrating docs tickets to Jira
Comments
pkj415
added a commit
to pkj415/yugabyte-db
that referenced
this issue
Dec 20, 2022
…llaneous related changes Apart from adding a docs page for "Concurrency control" in the architecture section, a "Transaction Priorities" page is also added. Other miscellaneous changes are done since we are moving away from the "Optimistic" and "Pessimistic" terminology which have been inaccurately used historically in our docs pages and internally for describing YugabteDB's concurrency control mechanism. For example, optimistic concurrency control (https://people.eecs.berkeley.edu/~fox/summaries/database/optimistic_concurrency.html) involves checking conflicts lazily are commit time, which is not the case with YugabyteDB's default concurrency control method (which we used to inaccurately call "Optimistic"). And we used to the Postgres-style of concurrency control, which involves waiting, as pessimistic. After much deliberation, our concurrency control policies are are being re-mapped to the following names in our docs pages- 1. What we used to call "Optimistic" -> Fail-on-Conflict 2. What we used to call "Pessimistic" -> Wait-on-Conflict Also, the docs/content/preview/explore/transactions/explicit-locking.md page is removed, because it has a lot of inaccurate information and was not even needed. The docs/content/preview/explore/transactions/explicit-locking.md page instead has all the neccesary information.
pkj415
changed the title
pkj415
added a commit
that referenced
this issue
Jan 15, 2023
… related changes (#14839) Apart from adding a docs page for "Concurrency control" in the architecture section, a "Transaction Priorities" page is also added. Other miscellaneous changes are done to move away from the terms "Optimistic" and "Pessimistic" which have been inaccurately used historically in our docs pages and internally for describing YugabteDB's concurrency control mechanisms. For example, optimistic concurrency control (https://people.eecs.berkeley.edu/~fox/summaries/database/optimistic_concurrency.html) involves checking conflicts lazily are commit time, which is not the case with YugabyteDB's default concurrency control method (which we used to inaccurately call "Optimistic"). And we used to call the Postgres-style of concurrency control, which involves transactions waiting on each other on conflicts, as "pessimistic". After much deliberation, our concurrency control policies are are being renamed to the following in our docs pages - 1. What we used to call "Optimistic" -> Fail-on-Conflict 2. What we used to call "Pessimistic" -> Wait-on-Conflict Also, the docs/content/preview/explore/transactions/explicit-locking.md page is removed, because it has a lot of inaccurate information and was not even needed. The docs/content/preview/explore/transactions/explicit-locking.md page instead has all the necessary information.
|
need to document deadlock detection behavior |
polarweasel
added
the
temp/docs-migration
|
closing in favor of #16203 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Update here: https://docs.yugabyte.com/preview/explore/transactions/distributed-transactions-ysql/#concurrency-control
And add a new page documenting usage, behavior, and best practices
The text was updated successfully, but these errors were encountered: