Skip to content
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.

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

[Content Bug] Edit page: /self-hosted/latest/upgrades/minor-upgrade/ #3714

Closed
rgvoz opened this issue Jan 16, 2025 · 1 comment · Fixed by #3719
Closed

[Content Bug] Edit page: /self-hosted/latest/upgrades/minor-upgrade/ #3714

rgvoz opened this issue Jan 16, 2025 · 1 comment · Fixed by #3719
Labels
bug Something isn't working documentation Improvements or additions to documentation

Comments

@rgvoz
Copy link

rgvoz commented Jan 16, 2025

Use this template for reporting bugs in the docs.

Describe the bug

The compatibility matrix on the referenced page indicates TimescaleDB extensions in the 2.16.x releases are compatible with PostgreSQL 13.

However, attempting to build TimescaleDB extension v2.16.1 for PostgreSQL 13.18 on macOS 15.2/Mac Mini M4 fails with message

CMake Error at CMakeLists.txt:355 (message):
  TimescaleDB only supports PostgreSQL 14, 15 and 16

I am able to build e.g. v2.15.3 against the same installation of PostgreSQL 13.18

What do the docs say now?

Version numberPostgreSQL 17PostgreSQL 16PostgreSQL 15PostgreSQL 14PostgreSQL 13PostgreSQL 12PostgreSQL 11PostgreSQL 10
TimescaleDB
2.16.x

What should the docs say?

If not an isolated case, this incompatibility should be reflected in the compatibility matrix, i.e.

Version numberPostgreSQL 17PostgreSQL 16PostgreSQL 15PostgreSQL 14PostgreSQL 13PostgreSQL 12PostgreSQL 11PostgreSQL 10
TimescaleDB
2.16.x

Page affected

https://docs.timescale.com/self-hosted/latest/upgrades/minor-upgrade/#plan-your-upgrade-path

@rgvoz rgvoz added bug Something isn't working documentation Improvements or additions to documentation labels Jan 16, 2025
@philkra
Copy link
Contributor

philkra commented Jan 17, 2025

Thank you for reporting this @rgvoz, you are correct. We dropped support for Postgres 13 with the 2.16.0 release. We'll update the docs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working documentation Improvements or additions to documentation
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants