Troubleshooting

    `

    `

    In some cases, when you create the TimescaleDB Toolkit extension, or upgrade it with the command, it might fail with the above error.

    This occurs if the list of available extensions does not include the version you are trying to upgrade to, and it can occur if the package was not installed correctly in the first place. To correct the problem, install the upgrade package, restart PostgreSQL, verify the version, and then attempt the update again.

    1. Update your local repository list with apt update or yum update.

    2. Restart your PostgreSQL service.

      The result should look like this:

    4. Retry CREATE EXTENSION or ALTER EXTENSION.

    `

    1. ERROR: could not access file "timescaledb-<VERSION>": No such file or directory

    `

    If the error occurs immediately after updating your version of TimescaleDB and the file mentioned is from the previous version, it is probably due to an incomplete update process. Within the greater PostgreSQL server instance, each database that has TimescaleDB installed needs to be updated with the SQL command ALTER EXTENSION timescaledb UPDATE; while connected to that database. Otherwise, the database will be looking for the previous version of the timescaledb files.

    See for more info.

    `

    When you use the command to upgrade, this error might appear.

    This occurs if you don’t run ALTER EXTENSION timescaledb UPDATE command as the first command after starting a new session using psql or if you use tab completion when running the command. Tab completion triggers metadata queries in the background which prevents the alter extension from being the first command.

    To correct the problem, execute the ALTER EXTENSION command like this:

    ``sql psql -X -c ‘ALTER EXTENSION timescaledb UPDATE;’

    `

    `

    In some cases, when you use the ALTER EXTENSION timescaledb UPDATE command to upgrade, it might fail with the above error.