Thank you for one of the best open source products ever. Our TimescaleDB had a solid uptime of > 500 days, but now some dark clouds have appeared in the horizon.
Our TimescaleDB server has started to crash in the background worker “Refresh Continuous Aggregate Policy”.
2025-04-02 11:47:29.839 UTC [1] LOG: background worker "Refresh Continuous Aggregate Policy [1045]" (PID 79357) was terminated by signal 11: Segmentation fault
2025-04-02 11:47:29.839 UTC [1] DETAIL: Failed process was running: CALL _timescaledb_internal.policy_refresh_continuous_aggregate()
--
We can reliably reproduce the crash by just running the database, though not sure about the trigger conditions yet.
After SIGSEGV PostgreSQL falls into recovery mode,
What would be the best way
- To diagnose what is the cause: get a human-readable stack trace
- Dig through release notes and GitHub to see if this has been fixed in a later version
TimescaleDB version 2.7.2, running the official timescale/timescaledb:2.7.2-pg14 Docker image.
1 post - 1 participant