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
As it stands, if there are consistent blocking queries against a table, safely_acquire_lock_for_table will loop indefinitely trying to acquire the lock. Would it make sense for this method to optionally take a timeout / retry limit argument such that it eventually exits and raises an error?