-
Notifications
You must be signed in to change notification settings - Fork 1k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[BACKPORT 2.8][#11165] YSQL: Detect conflict in case of INSERT from 2…
… SERIALIZABLE txns Summary: The D11239 / 83a150b introduces the optimization for UPDATE statement based on relaxing lock intent strength. After the change UPDATE of particular row takes `weak read` intent instead of `strong read` intent. This is achieved by creating `strong read` intent on row's `kLivenessColumn` column instead of row key itself. But this change introduces the bug that INSERT/UPSERT tries to create `strong read` intent on `kLivenessColumn` as well. Solution is to limit intent relaxing optimization for UPDATE operation only. Original commit: 7333ee7 / D16278 Test Plan: Jenkins New unit tests were introduced ``` ./yb_build.sh --gtest_filter PgMiniTest.DuplicateInsert* ./yb_build.sh --gtest_filter PgMiniTest.DuplicateUniqueIndexInsert* ./yb_build.sh --gtest_filter PgMiniTest.DuplicateNonUniqueIndexInsert* ``` Reviewers: mbautin, sergei, pjain, mihnea Reviewed By: mihnea Differential Revision: https://phabricator.dev.yugabyte.com/D16433
- Loading branch information
1 parent
b09e610
commit 4f52493
Showing
2 changed files
with
106 additions
and
14 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters