Database Level Locks

A database level lock is taken on the database that the operation is operating on. While an operation holds a database level lock, no other operation that requires the same lock can operate on that database.
A database level lock can be taken concurrently with locks on other databases in the same cluster. For example, two ALTERs can run simultaneously on two different databases.
If a database level lock is taken, it will block a cluster lock from being taken.
DML operations are not affected by these locks.
DDL operations that are affected by these locks are listed in Operations that Take Database Level Locks.
Any blocked operations will queue.

Example: Database a takes a shared lock to perform CREATE DATABASE. Database b takes a shared lock to perform BACKUP DATABASE concurrently.

Last modified: August 30, 2022

Was this article helpful?

Verification instructions

Note: You must install cosign to verify the authenticity of the SingleStore file.

Use the following steps to verify the authenticity of singlestoredb-server, singlestoredb-toolbox, singlestoredb-studio, and singlestore-client SingleStore files that have been downloaded.

You may perform the following steps on any computer that can run cosign, such as the main deployment host of the cluster.

(Optional) Run the following command to view the associated signature files.
Shell
```
curl undefined
```
Download the signature file from the SingleStore release server.
- Option 1: Click the Download Signature button next to the SingleStore file.
- Option 2: Copy and paste the following URL into the address bar of your browser and save the signature file.
- Option 3: Run the following command to download the signature file.
  Shell
```
curl -O undefined
```

After the signature file has been downloaded, run the following command to verify the authenticity of the SingleStore file.

Shell

echo -n undefined |
    cosign verify-blob --certificate-oidc-issuer https://oidc.eks.us-east-1.amazonaws.com/id/CCDCDBA1379A5596AB5B2E46DCA385BC \
      --certificate-identity https://kubernetes.io/namespaces/freya-production/serviceaccounts/job-worker \
      --bundle undefined \
      --new-bundle-format -

Verified OK