Mats Kindahl

> Seems so, I'm fine with closing mine in that case, but let this serve as my emphatic +1 :) This provides a good example and API description compared to...

Here is a different failure: https://github.com/timescale/timescaledb-private/actions/runs/9076173967/job/24938328350?pr=1106. Still one of the skip scan tests through. ``` diff -u /home/runner/work/timescaledb-private/timescaledb-private/tsl/test/expected/plan_skip_scan-15.out /home/runner/work/timescaledb-private/timescaledb-private/build/tsl/test/results/plan_skip_scan-15.out --- /home/runner/work/timescaledb-private/timescaledb-private/tsl/test/expected/plan_skip_scan-15.out 2024-05-14 08:27:20.150121414 +0000 +++ /home/runner/work/timescaledb-private/timescaledb-private/build/tsl/test/results/plan_skip_scan-15.out 2024-05-14 08:41:36.375585744 +0000 @@...

Hello @igor2x and thanks for the bug report. >It looks like, to my surprise, data in my chunks are really super "fragmented" (non-clustered) and I need to cluster them, to...

Another failure: https://github.com/timescale/timescaledb-private/actions/runs/8717126386/job/23911872955?pr=1112 ``` diff -u /home/runner/work/timescaledb-private/timescaledb-private/test/expected/chunk_utils.out /home/runner/work/timescaledb-private/timescaledb-private/build/test/results/chunk_utils.out --- /home/runner/work/timescaledb-private/timescaledb-private/test/expected/chunk_utils.out 2024-04-17 06:12:03.185235230 +0000 +++ /home/runner/work/timescaledb-private/timescaledb-private/build/test/results/chunk_utils.out 2024-04-17 06:18:00.156596918 +0000 @@ -959,13 +959,14 @@ \set ECHO errors Different Rows | Total Rows...

This seems like it could be related to https://github.com/timescale/timescaledb/pull/6717, which would make `COPY` the problem. A workaround for this would be to use `INSERT` instead of `COPY` or decompress the...

@hostops I tried to reproduce it in different ways but have not yet succeeded. Can you get access to the stack trace for the crash or show more in the...

@hostops Definitely delete failing then, so #6717 will not solve this issue. If you have a stack trace that would help a lot since it is hard to figure out...

> I just tested simple delete query in compressed chunk and bug was reproduced. > > ``` > DELETE FROM signal WHERE id=738744145666 AND "time" BETWEEN '2023-10-01' AND '2023-11-02'; >...

> If you mean stack trace on client. I just executed this command using `psql`. > > If `log_min_messages=DEBUG5` and `log_min_error_statement=DEBUG5` would be enough for server, I can get it....

@hostops Yes, that is what I was looking for. Thanks!