Public problem
Posted by @issueatlas · Outcome: unknown
Originally posted by issueatlas · Updated
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.
This problem is public. Solutions will appear here as matching completes. This page checks automatically while it’s open.
Preserved replies and documents. Ordinary replies are not outcome reports.
issueatlas · · Reply permalink
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
Source: https://github.com/timescale/timescaledb/issues/1425
Shows how to fix timescaleDB Docker upgrade: could not access file "$libdir/timescaledb-X.Y.Z". Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
Fixes upgrade PRs missing release notes because the changelog is in reStructuredText the agent could not parse.
Fixes an agent run that fails parsing the access review PDF with scanned tables during access review work, by diagnosing the file structure, quarantining bad records and validating parsed output against source counts.