Package timescaledb-toolkit-postgresql-16 is not available (packagecloud still shows it)

[tonyalaribe]

Relevant system information:

• OS: Ubuntu 24.04
• PostgreSQL version 16.2
• TimescaleDB Toolkit version 1.18
• Installation method: ubuntu server

Describe the bug

sudo apt-get install timescaledb-toolkit-postgresql-16=1:1.18.0~ubuntu22.04 which is recommended on package cloud does not work: https://packagecloud.io/timescale/timescaledb/packages/ubuntu/jammy/timescaledb-toolkit-postgresql-16_1.18.0~ubuntu22.04_arm64.deb?distro_version_id=237

Seems the file used to exist but no longer exists.

[ignatiusreza]

Until distribution for noble is fixed, would it be recommended to use the one for jammy in Ubuntu 24.04?

[hugo-lovighi]

Any news about this issue ?

[tonyalaribe]

I eventually compiled it from source. Not sure this is this has been fixed.

On Thu, Aug 1, 2024, 19:37 hug0 @.***> wrote:

Any news about this issue ?

— Reply to this email directly, view it on GitHub https://github.com/timescale/timescaledb-toolkit/issues/799#issuecomment-2263605610, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABSCVASO3UIJM534FK4P7RDZPJW37AVCNFSM6AAAAABHSKNLAOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENRTGYYDKNRRGA . You are receiving this because you authored the thread.Message ID: @.***>

[mohag]

timescaledb-toolkit-postgresql-15 is missing on 24.04 as well

[Sh1ken]

Same problem still persist for timescaledb-toolkit-postgresql-16 on 24.04

[dn0]

Isn't this problem affecting only arm64/aarch64? The platform looks to be supported but deb packages are not provided.

[mohag]

Isn't this problem affecting only arm64/aarch64? The platform looks to be supported but deb packages are not provided.

When I checked, it was missing on amd64 (at time of my comment)

[ghostcipher1]

Facing same issue on self-hosted running PostgreSQL 16 and unable to install. I'm running Ubuntu 22.04.

[jbx1]

Same problem with timescaledb-toolkit-postgresql-17 on Ubuntu 24.04 LTS.

[feikesteenbergen]

Toolkit now has packages (as of 1.21.0) for Ubuntu 24.04 for PostgreSQL 15, 16 and 17.

[gjstreicher-ims]

The releases for noble (ubuntu 24.04) (including ones for the amd64 architecture) are now available on packagecloud.io, which is what the custom timescaledb PPA points to, but versions of timescaledb-toolkit-postgres-N have only been released for Postgres 15 and up.

So, despite both Postgres 14 and Timescaledb 2.19.3 installing on noble, Timescaledb Toolkit requires Postgres 15 and up on noble.

Why?

[svenklemm]

We usually align this with the range of major postgres versions supported by timescaledb which atm is 15-18

[gjstreicher-ims]

Once a particular postgres version stops being supported by Timescaledb, as with version 14, why aren't the libraries (.so files in /lib/postgresql/<version>/lib) included where previous versions left off as they are with timescaledb libraries?

For example, if I was to upgrade from Postgres v14 to Postgres v17 using pg_upgrade, then timescaledb would work fine because it has backwards compatibility via the /lib/postgresql/17/lib/timescaledb-2.19.0.so library, which is where Postgres v14 stops.

Though, when using timescaledb_toolkit, I only get the latest toolkit library as /lib/postgresql/17/lib/timescaledb_toolkit-1.22.0.so, which makes upgrading from Postgres v14 a pain.

Sure, I can manually run apt-cache madison timescaledb-toolkit-postgresql-17 to find that it has release versions of 1:1.22.0~ubuntu:22.04 (on jammy of course), 1:1.21.0~ubuntu22.04, and 1:1.19.0~ubuntu22.04.

Then I can identify the exact version my Postgresql v14 instance is using by running sudo -u postgres psql -p 5432 -d my_database -c '\dx', which reveals that my Postgres V14 instance is using Tookit 1.19.0.

Then I can manually downgrade my toolkit installation for Postgres v17 to that exact Toolkit version via sudo apt install timescaledb-toolkit-postgresql-17=1:1.19.0~ubuntu22.04 -y --allow-downgrades.

And then finally running pg_upgrade will work.

Now, why not just include ALL the previous libraries? You know, all the ones that are available for Toolkit for Postgres v17 on jammy when I install it so that pg_upgrade works out of the box?

Isn't that the definition of backwards compatibility?

I've actually written a script just for this purpose that wraps around sudo apt install timescaledb-toolkit-postgresql-17 that literally downloads each of these release versions as a debian package, extracts the relevant .so file and pastes it into /lib/postgresql/17/lib so that I can upgrade to Postgres v17 from any of the relevant previous Postgres versions. I'll also need to do this for future Postgres versions if some of them stop at Toolkit versions where latter ones continue as Toolkit develops.

I shouldn't have to do this.