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.

STATISTICS

This view contains statistics about table indexes. It displays one row per column per index.

Column Name

Description

TABLE_CATALOG

This value is always def.

TABLE_SCHEMA

The name of the related schema (database) that a given table belongs to.

TABLE_NAME

The name of the related table for a given index.

NON_UNIQUE

If the index can contain duplicates, this is 1. If the index cannot contain duplicates, this is 0.

INDEX_SCHEMA

The name of the schema (database) that a given index belongs to. This value is the same as TABLE_SCHEMA.

INDEX_NAME

The name of a given index. This is primary if the index is a primary key.

SEQ_IN_INDEX

The sequential number of a column within a given index.

COLUMN_NAME

The name of a column within a given index.

COLLATION

If a given column is sorted ascending within an index, this value is A. If the column is sorted descending, it is D. If the column is not sorted, it is NULL.

CARDINALITY

This column is unused and is present only for compatibility reasons, its value is always 0.

SUB_PART

This column is unused and is present only for compatibility reasons, its value is always NULL.

PACKED

This column is unused and is present only for compatibility reasons, its value is always NULL.

NULLABLE

Whether a given column can contain NULL values.

INDEX_TYPE

The type of index.

COMMENT

This column is unused and is present only for compatibility reasons, its value is always empty.

INDEX_COMMENT

This column is unused and is present only for compatibility reasons, its value is always empty.

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