Sign inTry Free

ADVANCED_HISTOGRAMS

Warning

SingleStore 9.0 gives you the opportunity to preview, evaluate, and provide feedback on new and upcoming features prior to their general availability. In the interim, SingleStore 8.9 is recommended for production workloads, which can later be upgraded to SingleStore 9.0.

This view contains information about histograms that have been collected by automatic statistics or using ANALYZE.

For more information about this command and which columns SingleStore collects histograms on, see Statistics and Sampling Tasks.

Each histogram provides information about the distribution of data in a column, and consists of several buckets - the groups/intervals among which data points are divided. Each histogram bucket is displayed as a row in this view.

Column Name

Description

DATABASE_NAME

The name of the database.

TABLE_NAME

The name of the table.

COLUMN_NAME

The name of the column.

JSON_KEY

When there is a histogram on a json_key as part of a json column, there's an entry here for each (column, json_key) pair. For non-json columns JSON_KEY is NULL.

TYPE

The data type of the column.

VERSION

Internal version number of the histogram format, which may change if the way histograms are stored is changed. Its current value is 100.

BUCKET_COUNT

The number of buckets in the histogram.

BUCKET_INDEX

The index for a given bucket within its histogram.

RANGE_MIN

The minimum value in a given bucket.

RANGE_MAX

The maximum value in a given bucket.

UNIQUE_COUNT

The number of distinct data values that are in a given bucket.

CARDINALITY

The number of rows in a given bucket.

UNIQUE_COUNT_CUMULATIVE

The cumulative number of distinct data values in this column, up to the current bucket index.

CARDINALITY_CUMULATIVE

The cumulative number of rows in this column, up to the current bucket index.

Last modified: March 8, 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