Skip to content

chore: update for available versions #4638

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
billy-the-fish wants to merge 5 commits into
base: latest
Choose a base branch
from
Open

chore: update for available versions #4638

Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
92afd13
chore: update for available versioins.
billy-the-fish Jan 13, 2026
72e1cf3
Merge branch 'latest' into 4634-feedback-page-docsself-hostedlatestup…
billy-the-fish Jan 14, 2026
2497003
Update _migrate_self_postgres_plan_migration_path.md
billy-the-fish Jan 14, 2026
56b2934
Update _migrate_self_postgres_plan_migration_path.md
billy-the-fish Jan 14, 2026
84981de
Merge branch 'latest' into 4634-feedback-page-docsself-hostedlatestup…
billy-the-fish Jan 14, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 12 additions & 7 deletions _partials/_migrate_self_postgres_plan_migration_path.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,22 +1,27 @@

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
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:
Copy link
Contributor

@atovpeko atovpeko Jan 14, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  1. The latest version supporting PG 13 is TimescaleDB 2.15.0, not 2.16.1, which is reflected in the matrix on this page and the release notes (https://github.com/timescale/timescaledb/blob/main/CHANGELOG.md).
  2. Why not upgrade to PG 15, 16, 17 OR 18 for the latest?

1. Upgrade $TIMESCALE_DB to 2.16.1 (last version fully supporting $PG 13)
1. Upgrade $PG to 15, 16, 17, or 18
1. Upgrade $TIMESCALE_DB to the latest available version (2.24.x or higher)

You may need to [upgrade to the latest $PG version][upgrade-pg] before you upgrade TimescaleDB. Also,
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 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.

<SupportMatrix />

[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/