With TimescaleDB 2.0 now available on Timescale Cloud (as of Jan 20, 2021) we wanted to provide more details about what the new version includes and how to address known breaking changes.You will be able to upgrade your services to TimescaleDB 2.0, at your discretion.

Before details on how to upgrade, we wanted to share a bit more about all the great new features in our milestone 2.0 release. Check out this blog post for more details, and a quick summary below:

  • Updated, more permissive licensing: making all of our enterprise features free and granting more rights to users.
  • Substantial improvements to Continuous Aggregates: improving APIs and giving users greater control over the process.
  • User-Defined Actions (new feature!): users can now define custom behaviors inside the database and schedule them using our job scheduling system.
  • New and improved informational views: including over hypertables, chunks, policies, and job scheduling.

Before completing the upgrade, we encourage you to read Changes in TimescaleDB 2.0 for a more detailed look at how some of the changes impact the way your applications and scripts interact with the updated API. Breaking changes affect settings and APIs related to continuous aggregates, compression, and data retention.

These have been modified to provide greater configuration transparency and flexibility, therefore we highly recommend verifying that settings were migrated correctly and that your applications are updated to work with the new APIs.

What this means for you

First, all new services created on Timescale Cloud will run 2.0 by default, as of Jan 20th.

Existing services can be upgraded to 2.0 via the following steps:

  • Apply any pending maintenance updates in the Timescale Cloud UI for each service you want to upgrade. This will expose the 2.0 upgrade path for the specific service you updated.
  • Connect to each database within the service that you want to upgrade, and run the following command. This command can be run regardless of your current TimescaleDB version:
$ ALTER EXTENSION timescaledb UPDATE TO “2.0.0”;
  • Follow the steps one through three outlined in our docs here to avoid the breaking API changes.

If you have any questions or want more guidance, just send us a message at support at timescale.com

Did this answer your question?