Click here to view and discuss this page in DocCommentXchange. In the future, you will be sent there automatically.
Releases the specified connection-scope mutex, if it is locked by the current connection.
RELEASE MUTEX [ owner.]mutex-name
The owner of the mutex. owner can also be specified using an indirect identifier (for example, `[@variable-name]`).
The name of the mutex. mutex-name can also be specified using an indirect identifier (for example, `[@variable-name]`).
The RELEASE MUTEX statement releases one instance of lock on the mutex. So, if a connection has locked the mutex multiple times, then only one lock on the mutex is released per RELEASE MUTEX statement.
An error is returned if the mutex was not locked by the current connection or if the release is being requested for a transaction-scope mutex.
The RELEASE MUTEX statement will succeed on a dropped mutex that is locked by the current connection.
You must have the UPDATE ANY MUTEX SEMAPHORE system privilege, or be the owner of the mutex.
Not in the standard.
The following statement releases the protect_my_cr_section mutex:
RELEASE MUTEX protect_my_cr_section;