timescale/timescaledb repository overview

An open-source time-series database optimized for fast ingest and complex queries. Engineered up from PostgreSQL, packaged as an extension.

Please note: there is no latest tag for this image. See below for further explanation.

⁠Notable tags

• latest-pg17 - The latest release based on PostgreSQL 17
• latest-pg16 - The latest release based on PostgreSQL 16
• latest-pg15 - The latest release based on PostgreSQL 15
• latest-pg14 - The latest release based on PostgreSQL 14
• Each release will also have those corresponding tags, e.g., 2.18.0-pg17, 2.18.0-pg16, 2.18.0-pg15, and 2.18.0-pg14

⁠Notable links

• Detailed instructions on how to use this Image - https://docs.timescale.com/self-hosted/latest/install/installation-docker/⁠
• TimescaleDB itself - https://github.com/timescale/timescaledb⁠
• This docker image's repo - https://github.com/timescale/timescaledb-docker⁠
• Our homepage - http://www.timescale.com/⁠

⁠Why is there no latest tag?

In general, it is usually a bad idea to track the latest tag for any Docker image, since you may get unexpectedly upgraded. For TimescaleDB, this is particularly problematic because not only can the version of TimescaleDB change, but also the version of PostgreSQL. If we wanted our latest tag to always be the latest of all dependencies, users could be updated between major versions of PostgreSQL, which requires a pg_upgrade step. That may cause more hassles for the operator than expected.

For these reasons, we do not offer a latest tag, but we do offer a 'latest' equivalent by publishing a latest tag for each PostgreSQL platform we support. For production systems, you should still be explicit about the version you want to use and not these latest tags, but at least you won't have to run a pg_upgrade step unexpectedly.