-
Notifications
You must be signed in to change notification settings - Fork 885
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Stats improvement for Uncompressed Chunks #5118
Conversation
d6ab8fa
to
0337af2
Compare
Codecov Report
@@ Coverage Diff @@
## main #5118 +/- ##
==========================================
- Coverage 90.70% 90.67% -0.03%
==========================================
Files 228 228
Lines 53106 52981 -125
==========================================
- Hits 48168 48040 -128
- Misses 4938 4941 +3
... and 4 files with indirect coverage changes 📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
0337af2
to
03c8c45
Compare
The issue also says:
Do we have to change it in this PR as well? |
Pull request was converted to draft
8445d94
to
ac6b54b
Compare
db715f9
to
b94e7ef
Compare
66e4bdf
to
6da5da4
Compare
Automated backport to 2.10.x not done: cherry-pick failed. Git status
|
Transparent decompress chunk was added into to ignore list due to the side effect of timescale#5118. This issue is to fix the flaky nature of the test.
Transparent decompress chunk was added into to ignore list due to the side effect of timescale#5118. This issue is to fix the flaky nature of the test.
Transparent decompress chunk was added into to ignore list due to the side effect of timescale#5118. This issue is to fix the flaky nature of the test.
Transparent decompress chunk was added into to ignore list due to the side effect of timescale#5118. This issue is to fix the flaky nature of the test.
Transparent decompress chunk was added into to ignore list due to the side effect of timescale#5118. This issue is to fix the flaky nature of the test.
Transparent decompress chunk was added into to ignore list due to the side effect of timescale#5118. This issue is to fix the flaky nature of the test.
Transparent decompress chunk was added into to ignore list due to the side effect of timescale#5118. This issue is to fix the flaky nature of the test.
Transparent decompress chunk was added into to ignore list due to the side effect of timescale#5118. This issue is to fix the flaky nature of the test.
Transparent decompress chunk was added into to ignore list due to the side effect of #5118. This issue is to fix the flaky nature of the test.
In old TSDB versions, we disabled autovacuum for compressed chunks to keep the statistics. However, this restriction was removed in timescale#5118, but no migration was performed to enable autovacuum for existing chunks.
In old TSDB versions, we disabled autovacuum for compressed chunks to keep the statistics. However, this restriction was removed in timescale#5118, but no migration was performed to enable autovacuum for existing chunks.
In old TSDB versions, we disabled autovacuum for compressed chunks to keep the statistics. However, this restriction was removed in timescale#5118, but no migration was performed to reset the custom autovacuum for existing chunks.
In old TSDB versions, we disabled autovacuum for compressed chunks to keep the statistics. However, this restriction was removed in timescale#5118, but no migration was performed to reset the custom autovacuum for existing chunks.
In old TSDB versions, we disabled autovacuum for compressed chunks to keep the statistics. However, this restriction was removed in timescale#5118, but no migration was performed to reset the custom autovacuum for existing chunks.
In old TSDB versions, we disabled autovacuum for compressed chunks to keep the statistics. However, this restriction was removed in timescale#5118, but no migration was performed to reset the custom autovacuum for existing chunks.
In old TSDB versions, we disabled autovacuum for compressed chunks to keep the statistics. However, this restriction was removed in timescale#5118, but no migration was performed to reset the custom autovacuum setting for existing chunks.
In old TSDB versions, we disabled autovacuum for compressed chunks to keep the statistics. However, this restriction was removed in timescale#5118, but no migration was performed to reset the custom autovacuum setting for existing chunks.
In old TSDB versions, we disabled autovacuum for compressed chunks to keep the statistics. However, this restriction was removed in timescale#5118, but no migration was performed to reset the custom autovacuum setting for existing chunks.
In old TSDB versions, we disabled autovacuum for compressed chunks to keep the statistics. However, this restriction was removed in timescale#5118, but no migration was performed to reset the custom autovacuum setting for existing chunks.
In old TSDB versions, we disabled autovacuum for compressed chunks to keep the statistics. However, this restriction was removed in #5118, but no migration was performed to reset the custom autovacuum setting for existing chunks.
During the compression autovacuum use to be disabled for uncompressed chunk and enable after decompression. This leads to postgres maintainence issue. Let's not disable autovacuum for uncompressed chunk anymore. Let postgres take care of the stats in its natural way.
Fixes #3376 #4578 #4156