Compress_chunk_time_interval weird behavior over chunk interval

TimescaleDB and PostgreSQL
1

We have started to use compress_chunk_time_interval and after using it we have seen a new error regarding a constraint we are not aware of. When we try to insert a new row we get error:
Error: new row for relation “_hyper_198_440400_chunk” violates check constraint “constraint_427027”
DETAIL: Failing row contains (26213, 2021-02-26 07:00:00+00, 0.000, 2024-09-17 12:45:34.327421+00, 2025-02-18 13:34:18.674494+00, 2024-09-17 12:45:34.327421+00).

It seems to happen when we try to insert rows that span over two compressed chunk intervals.

2

Hi @Tristan, this seems to be because your backfill is just going over multiple chunks, and I tried to add them in the same chunk. I’d recommend you create an issue on GitHub, so it can be fixed by the core team.

Temporarily, you can try to break down your batches by the limits of your chunk ranges. You can get this information from the view here: Timescale documentation