Sign inTry Free

COLUMNAR_SEGMENTS

This view stores information about each columnar_segment (column segment).

The view does not include information about deleted segment files that have yet to be garbage collected.

Column Name

Description

DATABASE_NAME

The name of the related database.

TABLE_NAME

The name of the related table.

COLUMN_NAME

The name of the related column.

SEGMENT_ID

The ID of a given segment.

COLUMN_ID

The ID of the related column.

FILE

The name of the file where a given segment is stored relative to the data directory of the node.

HOST

The hostname or IP address for the related leaf node.

PORT

The port number of the related leaf node.

NODE_ID

The ID of the related leaf node.

PARTITION

The ID of the partition on which a given segment is stored.

ROWS_COUNT

The number of rows in a given segment.

DELETED_ROWS_COUNT

The number of deleted rows in a given segment.

ENCODING

The encoding for a given column.

MIN_VALUE

The minimum value of a given column in the segment.

MAX_VALUE

The maximum value of a given column in the segment.

SEGMENT_MIN_VALUE

The minimum value of the sort key column(s) in a given segment.

SEGMENT_MAX_VALUE

The maximum value of the sort key column(s) in a given segment.

UNCOMPRESSED_SIZE

The uncompressed size of a given columnar segment in bytes. Uncompressed size is the total size of your data before it is compressed by SingleStore. Does not include index data.

COMPRESSED_SIZE

The compressed size of a given columnar segment in bytes. Compressed size is the total size of your data after SingleStore has compressed it into a columnar table. SingleStore handles this compression automatically. Does not include index data.

CREATION_TIME

The timestamp when a given columnstore file was created.

LSN

Log sequence number of the related blob file.

TERM

The term of the database, used to uniquely identify which node was the master of a specific database.

CHECKSUM

The crc32c checksum of the file contents.

FILE_OFFSET

Specifies the offset in the file where a given segment is stored.

Last modified: October 16, 2025

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