SHOW TABLE STATUS

Show tables status information in a SingleStore database.

Syntax

SHOW TABLE STATUS [{FROM | IN} db_name]

Remarks

  • db_name is the name of a SingleStore database.

  • Shows how much memory this table is using for row data.

  • Memory for off-row data (such as VARCHARs) is not reported.

  • This command can be run on any SingleStore node (see Node Requirements for SingleStore Commands).

Output

Column

Description

Check_time

Default is null, used as a placeholder for MySQL compatibility

Engine

SingleStore engine image name

Version

Engine version

Row_format

Shows whether the table is a sparse compressed rowstore table

Rows

Number of rows in the table

Avg_row_length

Average memory used per row in the table and is calculated as Data_length / Rows

Data_length

Total memory used for a table

Max_data_length

Maximum data length. Default is null, used as a placeholder for MySQL compatibility.

Index_length

Index length. Default is null, used as a placeholder for MySQL compatibility.

Data_free

Data free. Default is null, used as a placeholder for MySQL compatibility.

Auto_increment

Default is null, used as a placeholder for MySQL compatibility.

Create_time

Table creation date and time

Update_time

Update time

Check_time

Default is null, used as a placeholder for MySQLcompatibility

Collation

Takes the default value as per the character set and collation engine variables. By default it is utf8_general_ci.

Checksum

Default is null, used as a placeholder for MySQL compatibility.

Create_options

Default is null, used as a placeholder for MySQL compatibility.

Comment

Comments

BuffMgr Memory Use

Buffer manager memory in use (in bytes)

Average GC Duration (ms)

Average duration of garbage collection (in milliseconds)

Example

show table status \G
*** 1. row ***
                    Name: x
                  Engine: MemSQL
                 Version: 10
              Row_format: Uncompressed
                    Rows: 130
          Avg_row_length: NULL
             Data_length: NULL
         Max_data_length: NULL
            Index_length: NULL
               Data_free: NULL
          Auto_increment: NULL
             Create_time: 2014-03-05 16:10:36
             Update_time: NULL
              Check_time: NULL
               Collation: utf8_general_ci
                Checksum: NULL
          Create_options: Not Available
                 Comment: Not Available
      BuffMgr Memory Use: 141472
Average GC Duration (ms): 0
1 row in set (0.00 sec)

Last modified: February 23, 2024

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