Sign inTry Free

TABLE_STATISTICS and INTERNAL_TABLE_STATISTICS

On this page

This view contains information about table statistics. It contains one row per table, per partition. INTERNAL_TABLE_STATICS (an internal use-only table added in v7.8) contains the same columns, and shows information for SingleStore internal metadata tables.

This information can be useful for Detecting and Resolving Data Skew.

Column Name

Description

DATABASE_NAME

The name of the related database.

TABLE_NAME

The name of the related table.

ORDINAL

The partition ID number.

HOST

The hostname or IP address for the related node.

PORT

The port number of the related node.

NODE_TYPE

The type of node: master aggregator (MA), child aggregator (CA), or leaf node (LEAF).

PARTITION_TYPE

The type of partition: master or secondary.

ROWS

The number of rows in a given table and partition.

MEMORY_USE

The memory use, in bytes, of a given table and partition.

STORAGE_TYPE

The storage type of a given table and partition.

ROWS_IN_MEMORY

The number of rows stored in memory for a given table and partition.

STORAGE_ID

Storage Id of the database.

COMPUTE_ID

Compute Id of the database.

Metadata Table Listing

The following metadata tables can be included in the INTERNAL_TABLE_STATISTICS.TABLE_NAME column:

Component

Table Name

Description

Columnstore

md_committed_blobs

Stores file-level information about columnstore data files.

Columnstore

md_gc_blobs

Stores information about columnstore data files that has been logically deleted.

Columnstore

md_columnar_sec_index

Stores information about on-disk index blobs created for columnstore secondary hash indexes.

Columnstore

md_blob_deletion_lsns

Stores more information about columnstore data files that have been logically deleted.

Columnstore

md_columnar_sec_index_is_built

For each columnstore secondary index added through an alter table statement, stores whether the index has been fully built or not.

Columnstore

md_columnar_blobs

Stores information about all column segments in the columnstore tables. The size of this table is proportional to the total row count and the column count across the columnstore tables. See for more info.

Columnstore

md_segments

Stores information about all row segments in the columnstore tables. The size of this table is proportional to the total row count across the columnstore tables. See How the Columnstore Works for more info.

Miscellaneous

md_bottomless_gc_deadlines

Stores information about unlimited storage GC deadlines used to support the unlimited storage retention period.

Miscellaneous

md_partition_instances

Tracks the states of the database partitions.

Miscellaneous

md_logical_partitions

Stores a mapping from logical partitions to the actual partitions.

Miscellaneous

md_queries

Deprecated.

Miscellaneous

md_attributes

Stores database-level attributes for internal use.

Miscellaneous

md_transaction_table

Tracks the states of ongoing distributed transactions.

Miscellaneous

md_transaction_outcome

Temporarily tracks the outcome of some distributed transactions.

Miscellaneous

md_task_queue

A queue of pending internal maintence tasks.

Miscellaneous

md_auto_incr_limit

For each auto increment column, stores an upper bound of previously generated auto increment values.

Pipelines

md_pipeline_transform_templates

Deprecated.

Pipelines

md_pipelines

For each auto increment column, stores an upper bound of previously generated auto increment values.

Pipelines

md_extractors_offsets

Contains information about a pipeline's offset ranges for every data source partition. That includes files for FS-like data sources, e.g. S3.

Pipelines

md_extractors

Deprecated.

Pipelines

md_pipelines_aux_files

Tracks on-disk files used for storing pipeline errors. It contains information such as file size, number of errors stored in a file, information about a table, pipeline, batches, etc.

Statistics

md_range_statistics

Deprecated. Replaced by md_advanced_histograms.

Statistics

md_advanced_histograms

Details all of the histograms that have been built in the cluster.

Statistics

md_column_statistics

Contains the cardinality stats for all user tables.

User Objects

md_credentials

Store the connection links created in the database.

User Objects

md_indexes

Stores the index definition for all tables.

User Objects

md_user_aggregate_params

Lists parameter definitions for each function in md_user_aggregates.

User Objects

md_indexColumns

Stores the list of columns contained in each index.

User Objects

md_user_aggregates

Lists all user defined aggregate function definitions. This includes PSQL, external, and Wasm aggregate functions.

User Objects

md_foreign_key_columns

Stores the list of columns contained in each foreign key.

User Objects

md_foreign_keys

Stores the foreign key definition for all tables.

User Objects

md_columns

Stores the column definition for all tables.

User Objects

md_user_functions

Lists all scalar UDF and TVF definitions. This includes PSQL, external, and Wasm functions.

User Objects

md_user_object_names

Lists all routine names from md_user_functions and md_user_aggregates.

User Objects

md_user_function_params

Lists parameter definitions for each function in md_user_functions.

User Objects

md_tables

List all tables in a database.

Last modified: July 31, 2025

Was this article helpful?

On this page

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