[Bug]: cache lookup failed for relation 0 - TimescaleDB tables

[jjosh23]

What type of bug is this?

Data corruption

What subsystems and features are affected?

Query executor

What happened?

Hi All,

Currently we are using TimescaleDB in windows machines. Some of the users has reported the following issue while trying to access the table.

ERROR: could not open relation with OID 0

Also in the logs we can see the below error too.
2024-10-21 08:45:04.679 IST [24140] ERROR: cache lookup failed for relation 0
2024-10-21 08:45:04.702 IST [7004] LOG: background worker "Retention Policy [1013]" (PID 24140) exited with exit code 1
2024-10-21 08:52:07.315 IST [12952] LOG: job 1009 threw an error

One thing which I noted was on the tables where Im getting the error has the compression and retention policies been set. For the tables without these policies it is working fine. Even non-timescaledb tables are also working fine.

We got the dump from the user and when we tried to restore from our side we got the same issue while trying to query or delete the table.

Current PostGress Version is 14.5
TimescaledbVersion: 2.7.2

Can you please help on this? We could not see any other error messages here.

TimescaleDB version affected

2.7.2

PostgreSQL version used

14.5

What operating system did you use?

Windows 10

What installation method did you use?

Source

What platform did you run on?

Other

Relevant log output and stack trace

No response

How can we reproduce the bug?

No. We are not able to reproduce the bug in our machines.

[akuzm]

The 2.7.2 is more than two years old, the current version is 2.17.1. Is it possible for you to upgrade?

[jjosh23]

Hi,

Thank you for the response.
Upgrading the timescaledb will not be quickest possible solution for us. Is there any ways to get the root cause of this issue?

Regards

[fabriziomello]

@jjosh23 without more detailed information is hard to even guess what is happening. About what table are u talking about? It is a normal table or a hypertable? Do u have the table definitions? What query is running that produce the error other than the retention policy failure?

As Alexander pointed out you're running a very old an unsupported tsdb version so the first advice is to update it to the last supported version 2.17.2.