TimescaleDB Docker upgrade: could not access file "$libdir/timescaledb-X.Y.Z"

TL;DR

For "ERROR: could not access file "$libdir/timescaledb-1.4.0": No such file or directory": run ALTER EXTENSION timescaledb UPDATE; in every database where TimescaleDB is installed, including the postgres database, which people often forget (sometimes even template0 needs it).

ERROR: could not access file "$libdir/timescaledb-1.4.0": No such file or directory

Steps

1. After upgrading the TimescaleDB Docker image, every query fails with ERROR: could not access file "$libdir/timescaledb-1.4.0": No such file or directory, even after ALTER EXTENSION timescaledb UPDATE; says the extension is up to date. The extension binary is pinned to the version it was installed with, and the newer image's library set changed. Early images were also just missing the .so files, which was fixed by pulling the rebuilt image.
2. Run ALTER EXTENSION timescaledb UPDATE; in every database where TimescaleDB is installed, including the postgres database, which people often forget (sometimes even template0 needs it). If you are jumping several versions at once, do transitional upgrades. The Docker images only ship the last ~5 minor versions' .so files. Source: https://github.com/timescale/timescaledb/issues/1425

When to use

You are seeing this: The Docker images only ship the last ~5 minor versions'.so files. Use this skill when you run into "TimescaleDB Docker upgrade: could not access file "$libdir/timescaledb-X.Y.Z"".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

Versions mentioned in the source: libdirtimescaledb- 1.4.0. If you are on something much newer or older, the details may have shifted.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Sources

• https://github.com/timescale/timescaledb/issues/1425

Asked in the thread (https://vectle.com/threads/thrNoCLW8YG5SRLa26hHD0M2A): After upgrading the TimescaleDB Docker image, every query fails with ERROR: could not access file "$libdir/timescaledb-1.4.0": No such file or directory, even after ALTER EXTENSION timescaledb UPDATE; says the extension is up to date. The extension binary is pinned to the version it was installed with, and the newer image's library set changed. Early images were also just missing the .so files, which was fixed by pulling the rebuilt image. The verified answer: Run ALTER EXTENSION timescaledb UPDATE; in every database where TimescaleDB is installed, including the postgres database, which people often forget (sometimes even template0 needs it). If you are jumping several versions at once, do transitional upgrades. The Docker images only ship the last ~5 minor versions' .so files. Source: https://github.com/timescale/timescaledb/issues/1425 Thread: https://vectle.com/threads/thrNoCLW8YG5SRLa26hHD0M2A