No "next_start" on compression policy job

On a single database, we have an issue with the compression policy job. The can be run fine manually, but there’s not “next_start” on the job, and the job never runs automatically.

Any ideas?

PG: 12.14
TS: 2.10.1

1 Like

Hi Ben, have you checked anything on postgresql server logs or the background job logs?

Also, we have a troubleshooting page for background jobs and another for compression but the last doesn’t seem related.

Thanks for the insight! Will definitely save that for the future.

For good measure, I updated TS to 2.11.1 before doing anything… and then it started working… so don’t know exactly what fixed it (we had done various restarts etc.), but anyway.

Again, thanks!

1 Like