Open tonygunter opened 3 weeks ago
I'm creating aggregates with no index because we have a single query that hits the data by product_id, profile_id, name, and bucket. The indexes are created after I populate the data in the views to gain a little speed on the initial inserts.
CREATE INDEX rz_minute_index ON rz_minute_downsample(product_id, profile_id, name, bucket);
CREATE INDEX rz_hour_index ON rz_hour_downsample(product_id, profile_id, name, bucket);
I can't seem to reproduce this behavior on version 2.16.1
Yeah, I was going to suggest trying it out on the later versions, 2.8.1 is pretty old at this point.
Definitely suggest upgrading as there have been major updates in the last 9 minor version.
What type of bug is this?
Unexpected error
What subsystems and features are affected?
Continuous aggregate
What happened?
Inserting data outside the refresh window results in a refresh that runs for several hours.
TimescaleDB version affected
2.8.1
PostgreSQL version used
14.6
What operating system did you use?
(Ubuntu 14.6-1.pgdg20.04+1) on x86_64-pc-linux-gnu
What installation method did you use?
Docker
What platform did you run on?
Amazon Web Services (AWS)
Relevant log output and stack trace
How can we reproduce the bug?