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
Reorder job fails because of already compressed chunks #1810
Labels
Comments
In the meantime, here is a workaround (specific to our domain model). The query marks all chunks as already reordered that are older than 28 days (our compression threshold). The reorder jobs have to be in place for this to work.
|
Olernov
added a commit
to Olernov/timescaledb
that referenced
this issue
Apr 26, 2020
Reorder policy does not skip compressed chunks when selecting next chunk to apply reordering. This causes an error in job execution since it's not possible to reorder compressed chunks. With this fix the job excludes compressed chunks from selection. Fixes timescale#1810
Olernov
added a commit
to Olernov/timescaledb
that referenced
this issue
Apr 26, 2020
Reorder policy does not skip compressed chunks when selecting next chunk to apply reordering. This causes an error in job execution since it's not possible to reorder compressed chunks. With this fix the job excludes compressed chunks from selection. Fixes timescale#1810
Olernov
added a commit
to Olernov/timescaledb
that referenced
this issue
May 6, 2020
Reorder policy does not skip compressed chunks when selecting next chunk to apply reordering. This causes an error in job execution since it's not possible to reorder compressed chunks. With this fix the job excludes compressed chunks from selection. Fixes timescale#1810
Olernov
added a commit
to Olernov/timescaledb
that referenced
this issue
May 6, 2020
Reorder policy does not skip compressed chunks when selecting next chunk to apply reordering. This causes an error in job execution since it's not possible to reorder compressed chunks. With this fix the job excludes compressed chunks from selection. Fixes timescale#1810
Olernov
added a commit
to Olernov/timescaledb
that referenced
this issue
May 7, 2020
Reorder policy does not skip compressed chunks when selecting next chunk to apply reordering. This causes an error in job execution since it's not possible to reorder compressed chunks. With this fix the job excludes compressed chunks from selection. Fixes timescale#1810
gayyappan
pushed a commit
that referenced
this issue
May 8, 2020
Reorder policy does not skip compressed chunks when selecting next chunk to apply reordering. This causes an error in job execution since it's not possible to reorder compressed chunks. With this fix the job excludes compressed chunks from selection. Fixes #1810
svenklemm
pushed a commit
that referenced
this issue
May 13, 2020
Reorder policy does not skip compressed chunks when selecting next chunk to apply reordering. This causes an error in job execution since it's not possible to reorder compressed chunks. With this fix the job excludes compressed chunks from selection. Fixes #1810
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Relevant system information:
PostgreSQL 11.6 (Debian 11.6-1.pgdg100+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 8.3.0-6) 8.3.0, 64-bit
Describe the bug
We use the following compression policy:
for this table
Now we have added a
but the job fails with
Expected behavior
We expected the job to finish by skipping already compressed chunks (as they cannot be changed and are already ordered).
The text was updated successfully, but these errors were encountered: