Skip to content

tidb_constraint_check_in_place_pessimistic should not be global scope, and should not affect internal sessions #38766

Closed
@ekexium

Description

Enhancement

Changing this variable can lead to unexpected results. Internals sessions shouldn't be affected by it as well, e.g. the imeplementation of get_lock() depends on tidb_contraint_check_in_place_pessimistic=1to work.
We should only allow sessions that are aware of its effects use it.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions