Sign inTry Free

Important

New database features are no longer connected to engine versions; features are now enabled independently during scheduled update windows, and “major” and “minor” releases no longer exist in Helios. Please visit the release notes to view the latest features available in your database clusters.

MV_MILESTONES

This view displays the list of milestones that have been created in the engine. This is the list of points that can be used to perform PITR.

_first_milestone , this milestone name is created automatically when a database is created. The other milestone names are created by explicitly using CREATE MILESTONE. If a name is not specified in the CREATE MILESTONE command, the milestone time will be used as the default milestone name.

MV_MILESTONES will not show milestones older than the retention period for unlimited storage databases.

Column name

Description

MILESTONE_NAME

Name of the milestone.

MILESTONE_TIME

Timestamp when milestone was created.

DATABASE_NAME

Name of the database for which the milestone is created.

DATABASE_LOCATION

The remote storage location of the database for which the milestone is created.

Example:

SELECT * FROM information_schema.MV_MILESTONES;
+----------------------------+----------------------------+---------------+-------------------+
| MILESTONE_NAME             | MILESTONE_TIME             | DATABASE_NAME | DATABASE_LOCATION |
+----------------------------+----------------------------+---------------+-------------------+
| _first_milestone           | 2021-11-10 11:44:25.956998 | x_db          | s3bucket          |
| 2021-11-10 11:44:27.911987 | 2021-11-10 11:44:27.911987 | x_db          | s3bucket          |
| x_db_milestone             | 2021-11-10 11:44:35.175052 | x_db          | s3bucket          |
+----------------------------+----------------------------+---------------+-------------------+

Last modified:

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