-
Notifications
You must be signed in to change notification settings - Fork 895
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
[Bug]: _timescaledb_internal.create_compressed_chunk
doesn't account for existing uncompressed rows
#5946
Labels
Comments
JamesGuthrie
changed the title
[Bug]:
[Bug]: Aug 9, 2023
_timescaledb_internal.create_compressed_chunk
doesn't account for existing uncompressed rows_timescaledb_internal.create_compressed_chunk
doesn't account for existing uncompressed rows
JamesGuthrie
added a commit
that referenced
this issue
Aug 10, 2023
`_timescaledb_internal.create_compressed_chunk` can be used to create a compressed chunk with existing compressed data. It did not account for the fact that the chunk can contain uncompressed data, in which case the chunk status must be set to partial. Fixes #5946
JamesGuthrie
added a commit
that referenced
this issue
Aug 10, 2023
`_timescaledb_internal.create_compressed_chunk` can be used to create a compressed chunk with existing compressed data. It did not account for the fact that the chunk can contain uncompressed data, in which case the chunk status must be set to partial. Fixes #5946
JamesGuthrie
added a commit
that referenced
this issue
Aug 10, 2023
`_timescaledb_internal.create_compressed_chunk` can be used to create a compressed chunk with existing compressed data. It did not account for the fact that the chunk can contain uncompressed data, in which case the chunk status must be set to partial. Fixes #5946
JamesGuthrie
added a commit
that referenced
this issue
Aug 10, 2023
`_timescaledb_internal.create_compressed_chunk` can be used to create a compressed chunk with existing compressed data. It did not account for the fact that the chunk can contain uncompressed data, in which case the chunk status must be set to partial. Fixes #5946
JamesGuthrie
added a commit
that referenced
this issue
Aug 10, 2023
`_timescaledb_internal.create_compressed_chunk` can be used to create a compressed chunk with existing compressed data. It did not account for the fact that the chunk can contain uncompressed data, in which case the chunk status must be set to partial. Fixes #5946
JamesGuthrie
added a commit
that referenced
this issue
Aug 10, 2023
`_timescaledb_internal.create_compressed_chunk` can be used to create a compressed chunk with existing compressed data. It did not account for the fact that the chunk can contain uncompressed data, in which case the chunk status must be set to partial. Fixes #5946
JamesGuthrie
added a commit
that referenced
this issue
Aug 10, 2023
`_timescaledb_internal.create_compressed_chunk` can be used to create a compressed chunk with existing compressed data. It did not account for the fact that the chunk can contain uncompressed data, in which case the chunk status must be set to partial. Fixes #5946
JamesGuthrie
added a commit
that referenced
this issue
Aug 23, 2023
`_timescaledb_internal.create_compressed_chunk` can be used to create a compressed chunk with existing compressed data. It did not account for the fact that the chunk can contain uncompressed data, in which case the chunk status must be set to partial. Fixes #5946
JamesGuthrie
added a commit
that referenced
this issue
Aug 23, 2023
`_timescaledb_internal.create_compressed_chunk` can be used to create a compressed chunk with existing compressed data. It did not account for the fact that the chunk can contain uncompressed data, in which case the chunk status must be set to partial. Fixes #5946
JamesGuthrie
added a commit
that referenced
this issue
Aug 23, 2023
`_timescaledb_internal.create_compressed_chunk` can be used to create a compressed chunk with existing compressed data. It did not account for the fact that the chunk can contain uncompressed data, in which case the chunk status must be set to partial. Fixes #5946
JamesGuthrie
added a commit
that referenced
this issue
Aug 23, 2023
`_timescaledb_internal.create_compressed_chunk` can be used to create a compressed chunk with existing compressed data. It did not account for the fact that the chunk can contain uncompressed data, in which case the chunk status must be set to partial. Fixes #5946
JamesGuthrie
added a commit
that referenced
this issue
Aug 23, 2023
`_timescaledb_internal.create_compressed_chunk` can be used to create a compressed chunk with existing compressed data. It did not account for the fact that the chunk can contain uncompressed data, in which case the chunk status must be set to partial. Fixes #5946
JamesGuthrie
added a commit
that referenced
this issue
Aug 23, 2023
`_timescaledb_internal.create_compressed_chunk` can be used to create a compressed chunk with existing compressed data. It did not account for the fact that the chunk can contain uncompressed data, in which case the chunk status must be set to partial. Fixes #5946
JamesGuthrie
added a commit
that referenced
this issue
Aug 24, 2023
`_timescaledb_internal.create_compressed_chunk` can be used to create a compressed chunk with existing compressed data. It did not account for the fact that the chunk can contain uncompressed data, in which case the chunk status must be set to partial. Fixes #5946
JamesGuthrie
added a commit
that referenced
this issue
Aug 24, 2023
`_timescaledb_internal.create_compressed_chunk` can be used to create a compressed chunk with existing compressed data. It did not account for the fact that the chunk can contain uncompressed data, in which case the chunk status must be set to partial. Fixes #5946
JamesGuthrie
added a commit
that referenced
this issue
Aug 24, 2023
`_timescaledb_internal.create_compressed_chunk` can be used to create a compressed chunk with existing compressed data. It did not account for the fact that the chunk can contain uncompressed data, in which case the chunk status must be set to partial. Fixes #5946
JamesGuthrie
added a commit
that referenced
this issue
Aug 24, 2023
`_timescaledb_internal.create_compressed_chunk` can be used to create a compressed chunk with existing compressed data. It did not account for the fact that the chunk can contain uncompressed data, in which case the chunk status must be set to partial. Fixes #5946
JamesGuthrie
added a commit
that referenced
this issue
Aug 28, 2023
`_timescaledb_internal.create_compressed_chunk` can be used to create a compressed chunk with existing compressed data. It did not account for the fact that the chunk can contain uncompressed data, in which case the chunk status must be set to partial. Fixes #5946
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What type of bug is this?
Incorrect result
What subsystems and features are affected?
Compression
What happened?
The
_timescaledb_internal.create_compressed_chunk
is an internal API which can be used to create a new compressed chunk using an existing table containing compressed data.This function assumes that it will only be applied to a chunk which does not contain uncompressed rows. When the uncompressed chunk contains rows, they "disappear" after calling this function (i.e. the
status
in the timescaledb catalog is incorrectly set to1
instead of9
on the uncompressed chunk).TimescaleDB version affected
2.11.1
PostgreSQL version used
15
What operating system did you use?
NixOS x64
What installation method did you use?
Docker
What platform did you run on?
Not applicable
Relevant log output and stack trace
No response
How can we reproduce the bug?
The text was updated successfully, but these errors were encountered: