Introducing Phased Rollouts for Safer TimescaleDB Upgrades

Production database upgrades are a high-stakes event. For any team managing critical applications, the process can be a source of significant anxiety. At TigerData, we believe you should be able to benefit from the latest database features and performance improvements without worrying about production stability.

That’s why we’re excited to announce Phased Rollouts, a new, safer upgrade process for all TimescaleDB services on Tiger Cloud. Starting today, all major and minor TimescaleDB version upgrades will be deployed in stages, giving you a three-week window to test and validate in your development environment before the update ever touches your production workloads.

This gives your team more time to observe a new release in real-world scenarios, catch any regressions specific to your workload, and ensure that every upgrade is a smooth, non-eventful process.

How Phased Rollouts Work

The process is simple, predictable, and automated. It applies to all major (e.g., 2.x.x→3.0.0) and minor (e.g., 2.21.x→2.22.0) version upgrades and is designed to give you maximum visibility with minimal effort.

1. Release: A new minor version of TimescaleDB becomes available.
2. Phase 1 (Development): The new version is automatically applied to all services you have tagged as dev during their next scheduled maintenance window.
3. Phase 2 (Validation): A three-week validation period begins. This gives your team ample time to test the upgrade against your applications, queries, and workloads in a safe, non-critical environment.
4. Phase 3 (Production): After the three-week period has passed, the upgrade is automatically applied to all services tagged as prod during their next maintenance window.

A Note on Patch Releases: This phased process applies to major and minor versions that introduce new features and functionality. Critical patch releases (e.g., 2.22.0→2.22.1), which contain important security or stability fixes, are an exception. To ensure your services are protected, patches are applied to all relevant services (both dev and prod) during the next available maintenance window.

The One Step to Safer Upgrades: Tag Your Services

Phased Rollouts are enabled for all customers today, but they are most effective when we know which of your services are for development and which are for production. Providing this context is the key to unlocking this new safety net.

To enable this protection for your workflow, apply the dev or prod label to your services in the Tiger Cloud console.

Handling Exceptions and Edge Cases

While Phased Rollouts make upgrades safer and more predictable, we recognize that every production environment has its own demands. You still maintain control over when an upgrade occurs within your chosen maintenance window. And in rare cases where you need additional time beyond the standard three-week validation period, you can request a temporary deferral by opening a support case.

If a bug or regression is discovered during the validation phase, that’s exactly what this process is designed to catch. Our team will pause the production rollout until the issue is resolved, ensuring that stability is never compromised.

Critical patch releases remain an exception to the phased approach: to protect your systems, these are always applied promptly to both development and production services.

Safer Upgrades, Greater Confidence

With Phased Rollouts, database upgrades no longer need to feel risky or disruptive. By giving your team a predictable three-week validation period, you can adopt the latest TimescaleDB features with confidence—knowing that your production workloads remain safe.

Start tagging your services today in the Tiger Cloud console to take full advantage of this safeguard, and enjoy smoother, safer upgrades with every release.