Skip to content

Commit 3a7feac

Browse files
chore: update for available versions (#4638)
* chore: update for available versioins. * Update _migrate_self_postgres_plan_migration_path.md Signed-off-by: Iain Cox <[email protected]> * Update _migrate_self_postgres_plan_migration_path.md Signed-off-by: Iain Cox <[email protected]> * chore: update on review. --------- Signed-off-by: Iain Cox <[email protected]>
1 parent 3d00693 commit 3a7feac

File tree

1 file changed

+12
-7
lines changed

1 file changed

+12
-7
lines changed
Lines changed: 12 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -1,22 +1,27 @@
11

22
import SupportMatrix from "versionContent/_partials/_migrate_self_postgres_timescaledb_compatibility.mdx";
33

4-
Best practice is to always use the latest version of TimescaleDB. Subscribe to our releases on GitHub or use $CLOUD_LONG
4+
Best practice is to always use the latest version of $TIMESCALE_DB. Subscribe to our releases on GitHub or use $CLOUD_LONG
55
and always run the latest update without any hassle.
66

7-
Check the following support matrix against the versions of $TIMESCALE_DB and $PG that you are running currently
7+
Check the following support matrix against the versions of $TIMESCALE_DB and $PG that you are running currently
88
and the versions you want to update to, then choose your upgrade path.
99

10-
For example, to upgrade from $TIMESCALE_DB 2.13 on $PG 13 to $TIMESCALE_DB 2.18.2 you need to:
11-
1. Upgrade $TIMESCALE_DB to 2.15
12-
1. Upgrade $PG to 14, 15 or 16.
13-
1. Upgrade $TIMESCALE_DB to 2.18.2.
10+
For example, to upgrade from $TIMESCALE_DB 2.13 on $PG 13 to the latest $TIMESCALE_DB version you need to:
11+
1. Upgrade $TIMESCALE_DB to 2.15.0 (last version fully supporting $PG 13)
12+
1. Upgrade $PG to 15, 16, 17, or 18
13+
1. Upgrade $TIMESCALE_DB to the latest available version (2.24.x or higher)
1414

15-
You may need to [upgrade to the latest $PG version][upgrade-pg] before you upgrade TimescaleDB. Also,
15+
Older $TIMESCALE_DB versions may not be available in package repositories. If you need a specific intermediate
16+
version that is no longer packaged, you can [build from source][build-from-source] or upgrade directly
17+
to the latest version that supports your current $PG version before upgrading $PG.
18+
19+
You may need to upgrade to the latest $PG version before you upgrade $TIMESCALE_DB. Also,
1620
if you use [$TOOLKIT_LONG][install-toolkit], ensure the `timescaledb_toolkit` extension is >=
1721
v1.6.0 before you upgrade $TIMESCALE_DB extension.
1822

1923
<SupportMatrix />
2024

2125
[install-toolkit]: /self-hosted/:currentVersion:/tooling/install-toolkit/
2226
[upgrade-pg]: /self-hosted/:currentVersion:/upgrades/upgrade-pg/#plan-your-upgrade-path
27+
[build-from-source]: /self-hosted/:currentVersion:/install/installation-source/

0 commit comments

Comments
 (0)