From 92afd139c899870666aef63be3068ec3df94a684 Mon Sep 17 00:00:00 2001 From: billy-the-fish Date: Tue, 13 Jan 2026 13:24:55 +0100 Subject: [PATCH 1/3] chore: update for available versioins. --- .../_migrate_self_postgres_plan_migration_path.md | 15 ++++++++++----- 1 file changed, 10 insertions(+), 5 deletions(-) diff --git a/_partials/_migrate_self_postgres_plan_migration_path.md b/_partials/_migrate_self_postgres_plan_migration_path.md index 466a08dc25..2c510f45f3 100644 --- a/_partials/_migrate_self_postgres_plan_migration_path.md +++ b/_partials/_migrate_self_postgres_plan_migration_path.md @@ -4,13 +4,17 @@ import SupportMatrix from "versionContent/_partials/_migrate_self_postgres_times Best practice is to always use the latest version of TimescaleDB. Subscribe to our releases on GitHub or use $CLOUD_LONG and always run the latest update without any hassle. -Check the following support matrix against the versions of $TIMESCALE_DB and $PG that you are running currently +Check the following support matrix against the versions of $TIMESCALE_DB and $PG that you are running currently and the versions you want to update to, then choose your upgrade path. -For example, to upgrade from $TIMESCALE_DB 2.13 on $PG 13 to $TIMESCALE_DB 2.18.2 you need to: -1. Upgrade $TIMESCALE_DB to 2.15 -1. Upgrade $PG to 14, 15 or 16. -1. Upgrade $TIMESCALE_DB to 2.18.2. +For example, to upgrade from $TIMESCALE_DB 2.13 on $PG 13 to the latest $TIMESCALE_DB version you need to: +1. Upgrade $TIMESCALE_DB to 2.16.1 (last version fully supporting $PG 13) +1. Upgrade $PG to 15, 16, or 17 +1. Upgrade $TIMESCALE_DB to the latest available version (2.24.x or higher) + +Older $TIMESCALE_DB versions may not be available in package repositories. If you need a specific intermediate +version that is no longer packaged, you can [build from source][build-from-source] or upgrade directly +to the latest version that supports your current $PG version before upgrading $PG. You may need to [upgrade to the latest $PG version][upgrade-pg] before you upgrade TimescaleDB. Also, if you use [$TOOLKIT_LONG][install-toolkit], ensure the `timescaledb_toolkit` extension is >= @@ -20,3 +24,4 @@ v1.6.0 before you upgrade $TIMESCALE_DB extension. [install-toolkit]: /self-hosted/:currentVersion:/tooling/install-toolkit/ [upgrade-pg]: /self-hosted/:currentVersion:/upgrades/upgrade-pg/#plan-your-upgrade-path +[build-from-source]: /self-hosted/:currentVersion:/install/installation-source/ From 24970036a4efa30f48b95294e965f32b9f8db6d7 Mon Sep 17 00:00:00 2001 From: Iain Cox Date: Wed, 14 Jan 2026 11:25:01 +0100 Subject: [PATCH 2/3] Update _migrate_self_postgres_plan_migration_path.md Signed-off-by: Iain Cox --- _partials/_migrate_self_postgres_plan_migration_path.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_partials/_migrate_self_postgres_plan_migration_path.md b/_partials/_migrate_self_postgres_plan_migration_path.md index 2c510f45f3..6a5f46ed1e 100644 --- a/_partials/_migrate_self_postgres_plan_migration_path.md +++ b/_partials/_migrate_self_postgres_plan_migration_path.md @@ -9,7 +9,7 @@ and the versions you want to update to, then choose your upgrade path. For example, to upgrade from $TIMESCALE_DB 2.13 on $PG 13 to the latest $TIMESCALE_DB version you need to: 1. Upgrade $TIMESCALE_DB to 2.16.1 (last version fully supporting $PG 13) -1. Upgrade $PG to 15, 16, or 17 +1. Upgrade $PG to 15, 16, 17, or 18 1. Upgrade $TIMESCALE_DB to the latest available version (2.24.x or higher) Older $TIMESCALE_DB versions may not be available in package repositories. If you need a specific intermediate From 56b29342fd8f0032ad6a3a2a6dd8fb07677f594c Mon Sep 17 00:00:00 2001 From: Iain Cox Date: Wed, 14 Jan 2026 11:28:18 +0100 Subject: [PATCH 3/3] Update _migrate_self_postgres_plan_migration_path.md Signed-off-by: Iain Cox --- _partials/_migrate_self_postgres_plan_migration_path.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/_partials/_migrate_self_postgres_plan_migration_path.md b/_partials/_migrate_self_postgres_plan_migration_path.md index 6a5f46ed1e..a09ecea223 100644 --- a/_partials/_migrate_self_postgres_plan_migration_path.md +++ b/_partials/_migrate_self_postgres_plan_migration_path.md @@ -1,7 +1,7 @@ import SupportMatrix from "versionContent/_partials/_migrate_self_postgres_timescaledb_compatibility.mdx"; -Best practice is to always use the latest version of TimescaleDB. Subscribe to our releases on GitHub or use $CLOUD_LONG +Best practice is to always use the latest version of $TIMESCALE_DB. Subscribe to our releases on GitHub or use $CLOUD_LONG and always run the latest update without any hassle. Check the following support matrix against the versions of $TIMESCALE_DB and $PG that you are running currently @@ -16,7 +16,7 @@ Older $TIMESCALE_DB versions may not be available in package repositories. If yo version that is no longer packaged, you can [build from source][build-from-source] or upgrade directly to the latest version that supports your current $PG version before upgrading $PG. -You may need to [upgrade to the latest $PG version][upgrade-pg] before you upgrade TimescaleDB. Also, +You may need to upgrade to the latest $PG version before you upgrade $TIMESCALE_DB. Also, if you use [$TOOLKIT_LONG][install-toolkit], ensure the `timescaledb_toolkit` extension is >= v1.6.0 before you upgrade $TIMESCALE_DB extension.