If the blocking option is set to On, any transaction attempting to obtain a lock that conflicts with an existing lock held
by another transaction waits until every conflicting lock is released or until the blocking_timeout is reached. If the lock
is not released within blocking_timeout milliseconds, then an error is returned for the waiting transaction. If the blocking
option is set to Off, the transaction that attempts to obtain a conflicting lock receives an error.
The value for the blocking connection property can be temporarily set to Off during certain operations (for example, refreshing
a materialized view), which can then also cause a SQLSTATE 42W18 and SQLCODE -210. See User '%1' has the row in '%2' locked.