Use the for no key update lock when upadting traversal ids
Updating traversal_ids for a namespace does require an update lock however we can use a weaker lock to avoid deadlocks in cases where multiple projects or namespaces are created concurently at the root namespace level due to KEY SHARE and UPDATE locks blocking each other. NO KEY UPDATE lock and KEY SHARE lock do not block each other.
Showing
Please register or sign in to comment