Open chicco785 opened 2 months ago
Hi! Sorry for the late reply here.
Looks like you are hitting a bug that's being addressed in version 2.15. Here is the link to the specific PR.
I'm keeping the ticket open since I'm not 100% sure this will solve all your performance problems here but its a step in the right direction. Would you mind updating us when 2.15 lands and you are able to test it? Release should be happening very soon (within the next week I believe).
Hope this helps!
Hi! Sorry for the late reply here.
Looks like you are hitting a bug that's being addressed in version 2.15. Here is the link to the specific PR.
I'm keeping the ticket open since I'm not 100% sure this will solve all your performance problems here but its a step in the right direction. Would you mind updating us when 2.15 lands and you are able to test it? Release should be happening very soon (within the next week I believe).
Hope this helps!
Thanks, we will surely test!
What type of bug is this?
Performance issue
What subsystems and features are affected?
Compression, Query executor, Query planner
What happened?
I have a compressed hypertable that stores data from 55 devices every 20ms.
The table is compressed as follows:
I am looking for an efficient query to extract the distinct couples of measurement_id and producer_id over a time range:
e.g.
or
These queries take more than 13 minutes to execute on my system, while given that I suppose finding the tuples should be possible just by looking at the indexes created by chunk segmentation, the query should be much faster :/
TimescaleDB version affected
2.13.0
PostgreSQL version used
15.5
What operating system did you use?
Ubuntu 22.04 x64
What installation method did you use?
Docker
What platform did you run on?
Amazon Web Services (AWS)
Relevant log output and stack trace
No response
How can we reproduce the bug?