Sign inTry Free

Important

The SingleStore 9.1 release candidate (RC) is available now. It will be promoted to general availability (GA) soon and at that time it will be renamed to SingleStore 10.

In the interim, SingleStore 9.1 RC can be used to preview, evaluate, and provide feedback on the new and upcoming features in SingleStore 10, while SingleStore 9.0 is recommended for production workloads.

MV_BOTTOMLESS_DATABASES

This view provides basic information about all the databases on an unlimited storage cluster. It includes databases currently attached on the cluster.

Column name

Description

DATABASE_NAME

Name of the database.

STORAGE_ID

The unique ID of the storage backing the unlimited storage database.

COMPUTE_ID

Compute ID of the database.

CREATED_TIME

Time at which the unlimited storage database was created.

IS_DETACHED

Values can be "DETACHED" or "ATTACHED" depending on whether the database is currently detached or attached.

RETENTION_PERIOD_MINUTES

Minimum period of time, in minutes, before GC will clean up remote storage.

Configured via bottomless_gc_retention_period_minutes.

EARLIEST_AVAILABLE_TIME

Earliest timestamp at which this database is attachable.

LAST_DETACHED_MILESTONE

The most recent milestone at which this database was detached.

STORAGE_CONFIG

The unlimited storage configuration information which with this database was created.

STORAGE_TYPE

The cloud service provider (S3/Azure/GCP) on which the storage for this unlimited storage database exists.

HAS_METADATA_SERVICE

Whether this database has the unlimited storage metadata service enabled.

MEMORY_USE_ON_DETACH

The memory usage, in bytes, of this unlimited storage database's storage at time of detach. NULL if the database is attached (this column is not used for tracking memory usage of active databases).

Example:

Version 8.5 and newer:

SELECT * FROM information_schema.MV_BOTTOMLESS_DATABASES;
+-----------------+------------------------------------------+-------------------------+---------------------+-------------+--------------------------+-------------------------+----------------------------+------------------------------------------------------+--------------+----------------------+----------------------+
| DATABASE_NAME   | STORAGE_ID                               | COMPUTE_ID              | CREATED_TIME        | IS_DETACHED | RETENTION_PERIOD_MINUTES | EARLIEST_AVAILABLE_TIME | LAST_DETACHED_MILESTONE    | STORAGE_CONFIG                                       | STORAGE_TYPE | HAS_METADATA_SERVICE | MEMORY_USE_ON_DETACH |
+-----------------+------------------------------------------+-------------------------+---------------------+-------------+--------------------------+-------------------------+----------------------------+------------------------------------------------------+--------------+----------------------+----------------------+
| attached_db     | 2396611468173586007:12754783369249135506 | 16632719075037216741:5  | 2023-09-12 12:00:02 | ATTACHED    | 1440                     | 2023-09-12 12:00:02     |                            | {"endpoint_url": "http://storage_provider_endpoint"} | S3           | 0                    | NULL                 |
| detached_db     | 7514729589540251805:4355643310554835616  | NULL                    | 2023-09-12 12:01:01 | DETACHED    | 1440                     | 2023-09-12 12:01:01     | 2023-09-12 12_01_17.682054 | {"endpoint_url": "http://storage_provider_endpoint"} | S3           | 0                    | 0                    |
+-----------------+------------------------------------------+-------------------------+---------------------+-------------+--------------------------+-------------------------+----------------------------+------------------------------------------------------+--------------+----------------------+----------------------+

Versions 7.6 through 8.1:

+-----------------+------------------------------------------+---------------------+-------------+--------------------------+-------------------------+----------------------------+------------------------------------------------------+--------------+--------------+
| DATABASE_NAME   | STORAGE_ID                               | CREATED_TIME        | IS_DETACHED | RETENTION_PERIOD_MINUTES | EARLIEST_AVAILABLE_TIME | LAST_DETACHED_MILESTONE    | STORAGE_CONFIG                                       | STORAGE_TYPE | MEMORY_USAGE |
+-----------------+------------------------------------------+---------------------+-------------+--------------------------+-------------------------+----------------------------+------------------------------------------------------+--------------+--------------+
| attached_db     | 2396611468173586007:12754783369249135506 | 2023-09-12 12:00:02 | ATTACHED    | 1440                     | 2023-09-12 12:00:02     |                            | {"endpoint_url": "http://storage_provider_endpoint"} | S3           | NULL         |
| detached_db     | 7514729589540251805:4355643310554835616  | 2023-09-12 12:01:01 | DETACHED    | 1440                     | 2023-09-12 12:01:01     | 2023-09-12 12_01_17.682054 | {"endpoint_url": "http://storage_provider_endpoint"} | S3           | 0            |
+-----------------+------------------------------------------+---------------------+-------------+--------------------------+-------------------------+----------------------------+------------------------------------------------------+--------------+--------------+

Last modified:

Was this article helpful?

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.

  1. (Optional) Run the following command to view the associated signature files.

    curl undefined

  2. 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.

      curl -O undefined

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

    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

Try Out This Notebook to See What’s Possible in SingleStore

Get access to other groundbreaking datasets and engage with our community for expert advice.

Sign UpLog In