Sign inTry Free

Configure the Retention Period for an Unlimited Storage Database

Note

Unlimited storage databases are not available in all editions of SingleStore. For more information, see SingleStore Editions.

The engine variable bottomless_gc_retention_period_minutes specifies how long historical information used to enable point-in-time recovery (PITR) is retained. The default value of is 1440 minutes. To override the default value, set the engine variable. For example, to set to the value to 3000 minutes:

SET GLOBAL bottomless_gc_retention_period_minutes = 3000;

Once a milestone reaches the retention period set by bottomless_gc_retention_period_minutes, it will no longer be available and will not appear in the MV_MILESTONES information schema table.

You cannot attach an unlimited storage database at a milestone or time that is not within the retention period. For example, suppose bottomless_gc_retention_period_minutes is 1440 minutes (1 day). On June 1 you create a milestone for a database d. On June 3, you would not be able to attach d at the milestone created on June 1 or at a point in time that occurred on June 1.

Last modified: May 5, 2023

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