You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We see a lot of lock timeouts due to the advisory lock. Right now, we see that the advisory lock uses the class name to determine the unique name. But in our case, we could scope the name more narrowly to the tenant since we know for sure that different tenants will not corrupt each other (we have closure tree on the Employee model that belongs to one Company). Would it make sense to be able to overwrite the lock name on runtime? In our case, we would love to add the company id, so we hold the lock only within a single tenant, minimizing contention.
The text was updated successfully, but these errors were encountered:
We see a lot of lock timeouts due to the advisory lock. Right now, we see that the advisory lock uses the class name to determine the unique name. But in our case, we could scope the name more narrowly to the tenant since we know for sure that different tenants will not corrupt each other (we have closure tree on the
Employee
model that belongs to oneCompany
). Would it make sense to be able to overwrite the lock name on runtime? In our case, we would love to add the company id, so we hold the lock only within a single tenant, minimizing contention.The text was updated successfully, but these errors were encountered: