Sign inTry Free

MV_CLOUD_BRANCHES

This view displays all databases and branches, and their properties.

This view is intended for internal SingleStore use. No additional information is available.

Note

This view is only applicable for SingleStore Helios.

Column Name

Description

ROW_NUMBER

A unique identifier for this row during the scan of this table. Serves to match PREV_ROW_NUMBER and has no other meaning. In particular it is not stable across different scans of the table.

STORAGE_ID

Storage ID of the database branch.

WORKSPACE_GROUP_ID

Workspace Group ID of the database branch.

DATABASE_NAME

Name of the database branch (Important identifier for branches, attaching existing database as a new name will result in a different branch). This is also non-unique since there may be multiple branches of the same database.

REGION

Name of region containing the Workspace Group of this database branch.

LATEST_COMPUTE_ID

Compute ID for the latest compute session in this database branch.

ATTATCH_TYPE

The attach type (create, PITR, restore, resume) that led to the creation of this database branch. Note: create, PITR, and restore are not to be considered the final/permanent type and may change to resume as the life-cycle of the branch evolves. This information is subject to the retention period and may change: 1 day (Standard) or 7 days (Enterprise).

PREV_ROW_NUMBER

ROW_NUMBER of the previous database branch (source of attach) , or NULL if one does not exist. Note, this information is subject to the retention period and may change: 1 day (Standard) or 7 days (Enterprise).

PREV_COMPUTE_ID

Compute ID of the previous database, subject to retention period:1 day (Standard) or 7 days (Enterprise).

PREV_WORKSPACE_GROUP_ID

Workspace Group ID of the previous database, subject to retention period: 1 day (Standard) or 7 days (Enterprise).

PREV_DATABASE_NAME

Name of the previous database, subject to retention period: 1 day (Standard) or 7 days (Enterprise).

PREV_REGION

Region of the previous database, subject to retention period: 1 day (Standard) or 7 days (Enterprise).

OLDEST_VERSION

The oldest PITR-able version of this database branch.

END_VERSION

If the database branch is detached, the detach version. Otherwise NULL.

LATEST_VERSION_LOWER_BOUND

The lower bound of the version that PITR-to-latest will attach to. In the event of a FAILOVER, this is a bound on the data which will be lost.

OLDEST_UNIX_TIMESTAMP

The matching timestamp of the OLDEST_VERSION.

END_UNIX_TIMESTAMP

The matching timestamp of the END_VERSION.

LATEST_UNIX_TIMESTAMP_LOWER_BOUND

The matching timestamp of the LATEST_VERSION_LOWER_BOUND.

LATEST_ATTACH_TIME

The approximate time of the latest attach to compute action(CREATE/ATTACH/RESTORE) of this database branch.

IS_DETACHED

Indicates whether the database branch was safely detached from all workspaces.

IS_ATTACHED_TO_THIS_COMPUTE

Indicates whether the database is attached to current workspace.

IS_DROPPED

Indicates whether this database branch has been dropped. The branch will be cleaned up subject to retention period: 1 day (Standard) or 7 days (Enterprise).

IS_ATTACHABLE

Whether the current branch is attachable.

ATTACH_SYNTAX

Syntax used to attach this database branch to a workspace.

ATTACH_MEMO

Optional memo during attach. Note: Some internal functions such as FAILOVER/FAILBACK may automatically populate this field.

BRANCH_COMPUTE_HISTORY

A list of compute_ids for compute sessions that make up this branch, starting with the earliest compute_id and ending with the latest_compute_id.

ATTACH_SOURCE_TIME

The approximate time of the source data this branch is attached on. For example, ATTACH x_db AS y_db AT TIME t1; will display t1 here for y_db). This field can be NULL if the branch was created by CREATE, or temporarily NULL waiting for background update.

This information is subject to the retention period: 3 days (Standard) or 7 days (Enterprise).

Last modified: November 18, 2024

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