MV_ROW_CHANGE_COUNTS

This view is primarily for internal use, SingleStore recommends using MV_COLLECTED_ROW_CHANGE_COUNTS instead.

This view returns a row for each partition of each table with autostats (automatic statistics) hosted in the cluster, along with a change count.

These statistics are in-memory and show the number of row changes (inserts, updates, and deletes) that have been applied to the table partition since it became online on the host. In-memory statistics do not persist across restarts.

The write behavior to the view is controlled via the following engine variables: change_count_write_interval and background_statistics_collection_interval

Column name

Description

table_name

The name of the table in the database.

database_name

The name of the database associated with the activity.

partition

The table partition in the database.

changed

The count of changes (inserts, updates, and deletes) for a table partition.

token

The token associated with the table partition.

An example query related to this view:

SELECT table_name, database_name, SUM(changed) FROM MV_ROW_CHANGE_COUNTS GROUP BY ALL;
+------------+---------------+--------------+
| table_name | database_name | sum(changed) |
+------------+---------------+--------------+
| t          | db1           |            3 |
| t2         | db1           |            0 |
+------------+---------------+--------------+

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